date:20220524

You have been subscribed to a public bug:

Hi,

My system is working fine with 5.13.0-40-generic kernel and nvidia-
driver-510...

Switching to 5.13.0-41 is messing something up...

Black screen after grub.

No graphic at all (black screen).

Further investigation show problems with the nvidia module :


--
nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=none,decodes=none:owns=none
NVRM: The NVIDIA GPU :01:00.0
NVRM: (PCI ID: 10de:1cb3) installed in this system has
NVRM: fallen off the bus and is not responding to commands.
nvidia: probe of :01:00.0 failed with error -1
NVRM: The NVIDIA probe routine failed for 1 device(s).
NVRM: None of the NVIDIA devices were initialized.
nvidia-nvlink: Unregistered the Nvlink Core, major device number 507
--

modules nvidia-* are present and installed :

--
dkms status
nvidia, 510.73.05, 5.13.0-40-generic, x86_64: installed
nvidia, 510.73.05, 5.13.0-41-generic, x86_64: installed
--

but they can't be modprobed :

---
modprobe: ERROR: could not insert 'nvidia': No such device
---

Reboot on the 5.13.0-40-generic solve the problem.

We are numerous users here to have the same behaviour...

Description:Ubuntu 20.04.4 LTS
Release:20.04

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


** Tags: bot-comment focal
-- 
nvidia module cant load with 5.13.0-41-generic
https://bugs.launchpad.net/bugs/1975494
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-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 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

2022-05-24 Thread Sebastien Bacher

you don't need to patch, just install the standard Ubuntu update
provided on bug #1974428

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

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  With 20.04 I used a wifi connection with a hotspot Telenet with following 
parametres:
  security : WPA2 entreprise
  authentification : tunneled TLS
  no AC certificat drequired
  inner authentication : MSCHAPV2(non EAP)
  user name: my id
  password : my pswd

  with 22.04 it doesn’t work anymore nor with the internal broadcom wifi
  nor with dongles (nor my Dlink 140 nor TP-link WN7200)

  This problem is only present with hotspot requesting an identification
  (user+pswd) awith hotspots without identification everything is OK

  in appendice some infos
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michelvlt   1725 F pulseaudio
   /dev/snd/pcmC0D0p:   michelvlt   1725 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2022-04-21 (7 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IpRoute:
   default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 
   10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 
   169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 
   192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 
600
  MachineType: Apple Inc. MacBookPro8,1
  NonfreeKernelModules: wl
  Package: wpa
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 87.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245B3640C91C81
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245B3640C91C81
  dmi.modalias: 
dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro8,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+subscriptions


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

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

This change was made by a bot.

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

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

Title:
  package linux-headers-generic-hwe-22.04 5.15.0.33.36 failed to
  install/upgrade: problèmes de dépendances - laissé non configuré

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dkms non paramétré. Je tente de la supprimer du système pour régler le
  problème.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-headers-generic-hwe-22.04 5.15.0.33.36
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue May 24 09:43:18 2022
  ErrorMessage: problèmes de dépendances - laissé non configuré
  InstallationDate: Installed on 2022-02-19 (93 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   docker0   no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. PH67A-D3-B3
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=/dev/sda5 
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.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-generic-hwe-22.04 5.15.0.33.36 failed to 
install/upgrade: problèmes de dépendances - laissé non configuré
  UpgradeStatus: Upgraded to jammy on 2022-02-19 (93 days ago)
  dmi.bios.date: 04/13/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: PH67A-D3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd04/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnPH67A-D3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnPH67A-D3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: PH67A-D3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1975494] Re: nvidia module cant load with 5.13.0-41-generic

2022-05-24 Thread schoubi

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

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

Title:
  nvidia module cant load with 5.13.0-41-generic

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

Bug description:
  Hi,

  My system is working fine with 5.13.0-40-generic kernel and nvidia-
  driver-510...

  Switching to 5.13.0-41 is messing something up...

  Black screen after grub.

  No graphic at all (black screen).

  Further investigation show problems with the nvidia module :

  
  --
  nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=none,decodes=none:owns=none
  NVRM: The NVIDIA GPU :01:00.0
  NVRM: (PCI ID: 10de:1cb3) installed in this system has
  NVRM: fallen off the bus and is not responding to commands.
  nvidia: probe of :01:00.0 failed with error -1
  NVRM: The NVIDIA probe routine failed for 1 device(s).
  NVRM: None of the NVIDIA devices were initialized.
  nvidia-nvlink: Unregistered the Nvlink Core, major device number 507
  --

  modules nvidia-* are present and installed :

  --
  dkms status
  nvidia, 510.73.05, 5.13.0-40-generic, x86_64: installed
  nvidia, 510.73.05, 5.13.0-41-generic, x86_64: installed
  --

  but they can't be modprobed :

  ---
  modprobe: ERROR: could not insert 'nvidia': No such device
  ---

  Reboot on the 5.13.0-40-generic solve the problem.

  We are numerous users here to have the same behaviour...

  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

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


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

[Kernel-packages] [Bug 1970392] Re: 22.04 USB devices do not work after sleep on Dell XPS 13 9370

2022-05-24 Thread Aaron Whitehouse

Just by way of update, this does not happen very often. It happened to
me again today after I have changed around which ports I have things in,
perhaps for the first time since I reported this a month ago. The same
Thunderbolt ports are not working after suspend, but the USB-C only port
works.

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

Title:
  22.04 USB devices do not work after sleep on Dell XPS 13 9370

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9370 that came with Ubuntu preinstalled. I have
  just completed a fresh install of 22.04 on it.

  When I suspend the laptop, the USB devices that were plugged in when I
  suspended do not work. Specifically, I had an Ethernet adapter and a
  USB-C monitor with a keyboard attached through it. The monitor display
  works as expected, but neither the keyboard nor the Ethernet adapter
  work after suspending.

  Interestingly, I can move the Ethernet adapter to the remaining USB-C
  port and it works correctly. Moving it back afterwards, it still does
  not work.

  Please let me know if there is anything more I can do to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aaron-work  35648 F pulseaudio
   /dev/snd/controlC0:  aaron-work  35648 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 10:36:09 2022
  InstallationDate: Installed on 2022-04-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:br1.12:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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


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

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

2022-05-24 Thread Vinay HM

In reply to comment 22
I have tried reproducing the fatal-error issue by using provided test kernel 
(linux-image-unsigned-5.18.0-4-generic_5.18.0-4.4_amd64.deb) and Issue is seen.
Attaching serial logs of the efforts.


** Attachment added: "fatalerror_testkernel"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917471/+attachment/5592562/+files/fatalerror_testkernel

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

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

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

Bug description:
  SRU Justification:

  [IMPACT]

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

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

  according to the hardware partner:

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

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

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

  The hardware partner did some bisection and observed the following:

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

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

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

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

  This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.

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

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

  The hardware partner has preemptively pulled our 5.4 tree, applied the

[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input

@kaihengfeng any other workaround ... ?

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

Title:
  [Regression] Unable to wake laptop using trackpad input

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to Ubuntu 22.04,
  the dell laptop no longer wakes up using trackpad movement/interaction.

  Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e.,
  Working On:
  Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10.

  NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31
  )

  Just to clarify: Suspend and Resume are working, trackpad is functional 
before and after suspend,
  But,
  Trackpad trigger to wakeup from suspend is not working.

  --

  $ cat /proc/version_signature > version.log
  => Ubuntu 5.15.0-27.28-generic 5.15.30

  -

  $ lsb_release -rd
  =>
  Description:Ubuntu 22.04 LTS
  Release:22.04

  -

  $ apt-cache policy linux-image-generic
  =>
  linux-image-generic:
    Installed: 5.15.0.27.30
    Candidate: 5.15.0.27.30
    Version table:
   *** 5.15.0.27.30 500
  500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 
Packages
  500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages

  -

  What I expected to happen:
  Laptop wakes-up from suspend on touchpad interaction

  -

  What happened:
  Laptop did not wakeup from suspend on touchpad interaction.

  Laptop woke up on the press of power button.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.27.30
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  monkey 5198 F wireplumber
   /dev/snd/controlC1:  monkey 5198 F wireplumber
   /dev/snd/seq:monkey 5195 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri May  6 12:40:22 2022
  InstallationDate: Installed on 2018-10-25 (1288 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 
2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau 
nouveau.modeset=0 vt.handoff=7
  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-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server

According to AHCI spec v1.3.1, "7.3 Native Hot Plug Support", once LPM
is enabled the hotplug needs to be disabled.

So I agree with 2), I think we should write document and let users know
how to change the LPM for hotplugging detection.

For 3) I don't think we need to change the way it works, because there
can be lots of corner cases to cover, and not all servers need AHCI
hotplug feature. We just need a good documentation to instruct users how
to disable it.

4) is kicking the can down the road, the same issue will re-appear once
those servers get upgraded.

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

Title:
  SATA device hot plug regression on AMD EPYC (Asus) server

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux
  version 5.4.0-109-generic", but it works on earlier version of " Linux
  version 5.4.0-42-generic"

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


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

[Kernel-packages] [Bug 1937924] Re: kernel upgrade via apt 5.11.0.1015-raspi kills the OS on Raspberry Pi4B

Thanks for the feedback. Closing the ticket. Please open a new ticket if
you come across the issue again in the future.

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

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

Title:
  kernel upgrade via apt 5.11.0.1015-raspi kills the OS on Raspberry
  Pi4B

Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  OK, so I've already killed three RPi4B Ubuntu installs (1 Ubuntu
  Server, 2 Xubuntu Desktops) by installing the recommended apt
  package(s) for the firmware and especially the kernel into version
  5.11.0.1015 -- I've already written a comprehensive summary on the
  issue on AskUbuntu's side @
  https://askubuntu.com/questions/1353872/raspberry-
  pi4b-64bit-21-04-5-11-kernel-trees-1014-raspi-1015-raspi-apt

  The Ubuntu Server one was a fresh one and I literally did nothing else
  except apt update and apt upgrade straight out of the box from an
  image that I etched using the latest version of 'rpi-imager'. I ran
  the OS from a never-before-used, fresh USB stick as my attempt to get
  some sort of a working boot loader that I could then try to rsync/copy
  to the boot parts of the other Ubuntu builds that were broken by this
  very same update. No such luck! I would expect a _lot_ of broken OS
  installs headed your way; I did try to contact the devs two weeks ago
  when my first system got fried due to getting the update from the
  'hirsute-proposed' repository ... Geez.

  Under the /var/log/ of my first fried OS, I have absolutely no errors
  or warnings, and I've included i.e. my 'dmesg' output as for the
  installed stuff here: https://paste.ubuntu.com/p/SXnzTTsNtS/ -- that
  indeed was the last time the system booted.

  I'm really in a tough spot due to this because now I've got two dead
  systems and no apparent solution to fix it! :(

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


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

[Kernel-packages] [Bug 1949278] Re: Sometimes getting console with purple text (xorg not starting)

Thanks for the feedback. Closing the ticket. Please open a new ticket if
you come across the issue again in the future.

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

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

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

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

Title:
  Sometimes getting console with purple text (xorg not starting)

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in linux-raspi source package in Impish:
  Won't Fix
Status in linux-raspi source package in Jammy:
  Fix Released

Bug description:
  Affected HW: Raspberry Pi 4B

  Sometimes I'm getting console with purple text and boot freezes.
  Able to switch to another console (with regular white on black font) and 
start display manager manually.

  Experiencing same problem with kernels 5.13.0-1010-raspi,
  5.13.0-1008-raspi, 5.11.0-1021-raspi.

  First time got this issue after upgrade to 21.10
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp2', '/dev/dsp1', 
'/dev/dsp', '/dev/snd/controlC2', '/dev/snd/pcmC2D0p', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', 
'/dev/sequencer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.10
  ImageMediaBuild: 20210421.1
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 
xHCI USB 3.0 Controller
  Lsusb:
   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
   /:  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
  Package: linux-meta-raspi (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vc4drmfb
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:61:DD:84 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 
root=/dev/mmcblk0p2 rootwait rootfstype=ext4 fixrtc pty.legacy_count=6 
zswap.enabled=1 net.ifnames=0
  ProcVersionSignature: Ubuntu 5.11.0-1021.22-raspi 5.11.22
  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.11.0-1021-raspi N/A
   linux-backports-modules-5.11.0-1021-raspi  N/A
   linux-firmware 1.201.1
  StagingDrivers: bcm2835_codec vc_sm_cma snd_bcm2835 bcm2835_v4l2 bcm2835_isp 
bcm2835_mmal_vchiq
  Tags:  arm64-image raspi-image impish staging
  Uname: Linux 5.11.0-1021-raspi aarch64
  UpgradeStatus: Upgraded to impish on 2021-08-31 (60 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:

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


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

[Kernel-packages] [Bug 1970392] Re: 22.04 USB devices do not work after sleep on Dell XPS 13 9370

BIOS update (which contains Thunderbolt firmware) can really make a
difference, please give it a try.

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

Title:
  22.04 USB devices do not work after sleep on Dell XPS 13 9370

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9370 that came with Ubuntu preinstalled. I have
  just completed a fresh install of 22.04 on it.

  When I suspend the laptop, the USB devices that were plugged in when I
  suspended do not work. Specifically, I had an Ethernet adapter and a
  USB-C monitor with a keyboard attached through it. The monitor display
  works as expected, but neither the keyboard nor the Ethernet adapter
  work after suspending.

  Interestingly, I can move the Ethernet adapter to the remaining USB-C
  port and it works correctly. Moving it back afterwards, it still does
  not work.

  Please let me know if there is anything more I can do to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aaron-work  35648 F pulseaudio
   /dev/snd/controlC0:  aaron-work  35648 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 10:36:09 2022
  InstallationDate: Installed on 2022-04-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:br1.12:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1962359] Re: Hibernation fails due to resource busy during swap file check

2022-05-24 Thread zyf0330

I am lucky that find the same problem here.
I use Ubuntu 21.10, and the error info is same `kernel:  PM: Image not found 
(code -16)`.
This is my swap info

NAME   TYPE  SIZE USED PRIO
/dev/nvme1n1p5 partition  32G   0B   -2

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

Title:
  Hibernation fails due to resource busy during swap file check

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hopefully, the automatically collected information is useful. The
  issue manifests when I try to hibernate the device. I see the
  following in the logs:

  ~$ journalctl --no-hostname -b -1 | tail -6
  Feb 25 08:23:54 systemd[1]: nvidia-hibernate.service: Deactivated 
successfully.
  Feb 25 08:23:54 systemd[1]: Finished NVIDIA system hibernate actions.
  Feb 25 08:23:54 systemd[1]: Starting Hibernate...
  Feb 25 08:23:54 kernel: PM: Image not found (code -16)
  Feb 25 08:23:54 systemd-sleep[50360]: Entering sleep state 'hibernate'...
  Feb 25 08:23:54 kernel: PM: hibernation: hibernation entry

  I looked up error code 16 as EBUSY. This happens when using pm-
  hibernate or "systemctl hibernate". I played qaround with the nvidia
  systemd hibernate units but it didn't help.

  Hibernate used to work before I upgraded to jammy. I was on focal and
  bionic before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-18-generic 5.15.0-18.18
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 26 09:27:29 2022
  InstallationDate: Installed on 2019-08-07 (933 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash 
resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 
vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: X399 AORUS XTREME-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X399 AORUS XTREME
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1975580] [NEW] Enable StarFive VisionFive board

2022-05-24 Thread Dimitri John Ledkov

Public bug reported:

Enable StarFive VisionFive board

Apply relevant patches to linux-riscv-5.17 kernel to enable visionfive
kernel flavour.

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

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

Title:
  Enable StarFive VisionFive board

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  Enable StarFive VisionFive board

  Apply relevant patches to linux-riscv-5.17 kernel to enable visionfive
  kernel flavour.

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


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

[Kernel-packages] [Bug 1975582] [NEW] [UBUNTU 20.04] rcu stalls with many storage key guests

You have been subscribed to a public bug:

---Problem Description---
There can be rcu stalls when running lots of large guests with storage keys:

[1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU
[1377614.579845] rcu:   18-: (2099 ticks this GP) 
idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 
[1377614.579895](t=2100 jiffies g=155867385 q=20879)
[1377614.579898] Task dump for CPU 18:
[1377614.579899] CPU 1/KVM   R  running task0 1030947 256019 
0x0604
[1377614.579902] Call Trace:
[1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0)
[1377614.579918]  [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 
[1377614.579919]  [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 
[1377614.579924]  [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 
[1377614.579926]  [<001f1eceb26c>] update_process_times+0x3c/0x80 
[1377614.579931]  [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 
[1377614.579932]  [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 
[1377614.579933]  [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 
[1377614.579935]  [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 
[1377614.579938]  [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 
[1377614.579942]  [<001f1f4c6d08>] ext_int_handler+0x130/0x134 
[1377614.579945]  [<001f1ec0af10>] ptep_zap_key+0x40/0x60 

 
Contact Information = cborn...@de.ibm.com 
 
---uname output---
 RELEASE: 5.4.0-90-generic
 VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021

== Comment: #1 - Christian Borntraeger  - 2022-05-24 
03:59:37 ==
This is a test patch that might address the rcu stalls.

== Comment: #2 - Christian Borntraeger  - 2022-05-24 
04:00:22 ==
This is a 2nd patch that reduces the cost of key setting.

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


** Tags: architecture-s39064 bugnameltc-198360 severity-medium 
targetmilestone-inin---
-- 
[UBUNTU 20.04] rcu stalls with many storage key guests
https://bugs.launchpad.net/bugs/1975582
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 1975582] patch that uses cheaper key setting variant

Default Comment by Bridge

** Attachment added: "patch that uses cheaper key setting variant"
   
https://bugs.launchpad.net/bugs/1975582/+attachment/5592578/+files/v2-0002-s390-pgtable-use-non-quiescing-sske-for-KVM-switc.patch

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

Title:
  [UBUNTU 20.04] rcu stalls with many storage key guests

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  There can be rcu stalls when running lots of large guests with storage keys:

  [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU
  [1377614.579845] rcu:   18-: (2099 ticks this GP) 
idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 
  [1377614.579895](t=2100 jiffies g=155867385 q=20879)
  [1377614.579898] Task dump for CPU 18:
  [1377614.579899] CPU 1/KVM   R  running task0 1030947 256019 
0x0604
  [1377614.579902] Call Trace:
  [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0)
  [1377614.579918]  [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 
  [1377614.579919]  [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 
  [1377614.579924]  [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 
  [1377614.579926]  [<001f1eceb26c>] update_process_times+0x3c/0x80 
  [1377614.579931]  [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 
  [1377614.579932]  [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 
  [1377614.579933]  [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 
  [1377614.579935]  [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 
  [1377614.579938]  [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 
  [1377614.579942]  [<001f1f4c6d08>] ext_int_handler+0x130/0x134 
  [1377614.579945]  [<001f1ec0af10>] ptep_zap_key+0x40/0x60 

   
  Contact Information = cborn...@de.ibm.com 
   
  ---uname output---
   RELEASE: 5.4.0-90-generic
   VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021

  == Comment: #1 - Christian Borntraeger  - 2022-05-24 
03:59:37 ==
  This is a test patch that might address the rcu stalls.

  == Comment: #2 - Christian Borntraeger  - 2022-05-24 
04:00:22 ==
  This is a 2nd patch that reduces the cost of key setting.

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


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

[Kernel-packages] [Bug 1962359] Re: Hibernation fails due to resource busy during swap file check

2022-05-24 Thread zyf0330

Sorry, I am wrong.
Previously, I set "resume=LABEL=Swap" into grub `GRUB_CMDLINE_LINUX` param, and 
got error msg `kernel: PM: Image not found (code -16)` and resume failed.
After change to set `resume=/dev/xxx-to-swap`, resume works.

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

Title:
  Hibernation fails due to resource busy during swap file check

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hopefully, the automatically collected information is useful. The
  issue manifests when I try to hibernate the device. I see the
  following in the logs:

  ~$ journalctl --no-hostname -b -1 | tail -6
  Feb 25 08:23:54 systemd[1]: nvidia-hibernate.service: Deactivated 
successfully.
  Feb 25 08:23:54 systemd[1]: Finished NVIDIA system hibernate actions.
  Feb 25 08:23:54 systemd[1]: Starting Hibernate...
  Feb 25 08:23:54 kernel: PM: Image not found (code -16)
  Feb 25 08:23:54 systemd-sleep[50360]: Entering sleep state 'hibernate'...
  Feb 25 08:23:54 kernel: PM: hibernation: hibernation entry

  I looked up error code 16 as EBUSY. This happens when using pm-
  hibernate or "systemctl hibernate". I played qaround with the nvidia
  systemd hibernate units but it didn't help.

  Hibernate used to work before I upgraded to jammy. I was on focal and
  bionic before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-18-generic 5.15.0-18.18
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 26 09:27:29 2022
  InstallationDate: Installed on 2019-08-07 (933 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash 
resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 
vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: X399 AORUS XTREME-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd12/11/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSXTREME:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSXTREME-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X399 AORUS XTREME
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1975582] Re: [UBUNTU 20.04] rcu stalls with many storage key guests

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

Title:
  [UBUNTU 20.04] rcu stalls with many storage key guests

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

Bug description:
  ---Problem Description---
  There can be rcu stalls when running lots of large guests with storage keys:

  [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU
  [1377614.579845] rcu:   18-: (2099 ticks this GP) 
idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 
  [1377614.579895](t=2100 jiffies g=155867385 q=20879)
  [1377614.579898] Task dump for CPU 18:
  [1377614.579899] CPU 1/KVM   R  running task0 1030947 256019 
0x0604
  [1377614.579902] Call Trace:
  [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0)
  [1377614.579918]  [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 
  [1377614.579919]  [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 
  [1377614.579924]  [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 
  [1377614.579926]  [<001f1eceb26c>] update_process_times+0x3c/0x80 
  [1377614.579931]  [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 
  [1377614.579932]  [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 
  [1377614.579933]  [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 
  [1377614.579935]  [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 
  [1377614.579938]  [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 
  [1377614.579942]  [<001f1f4c6d08>] ext_int_handler+0x130/0x134 
  [1377614.579945]  [<001f1ec0af10>] ptep_zap_key+0x40/0x60 

   
  Contact Information = cborn...@de.ibm.com 
   
  ---uname output---
   RELEASE: 5.4.0-90-generic
   VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021

  == Comment: #1 - Christian Borntraeger  - 2022-05-24 
03:59:37 ==
  This is a test patch that might address the rcu stalls.

  == Comment: #2 - Christian Borntraeger  - 2022-05-24 
04:00:22 ==
  This is a 2nd patch that reduces the cost of key setting.

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


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

[Kernel-packages] [Bug 1974434] Re: Black screen after grub with kernel 5.13.0-41-generic

2022-05-24 Thread Pavel Shvetsov

Samsung Series 9 Ultrabook (NP900X3D) - same problem

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

Title:
  Black screen after grub with kernel 5.13.0-41-generic

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

Bug description:
  After updating linux-image-generic-hwe-20.04 to 5.13.0-41-generic,

  After getting the 5.13.0-41-generic update from the linux-image-
  generic-hwe-20.04 package, I get a black screen right after the Grub
  menu is displayed.

  Selecting the previous kernel in the advanced menu of Grub fixes the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-generic-hwe-20.04 5.13.0.41.46~20.04.26
  ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 20 13:39:30 2022
  InstallationDate: Installed on 2017-01-11 (1954 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-hwe-5.13
  UpgradeStatus: Upgraded to focal on 2020-09-03 (623 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2017-01-11T16:59:14.311990

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


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

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

--- Comment From boris.m...@de.ibm.com 2022-05-24 06:15 EDT---
Released with Jammy, hence closing the bug
Changing status: -> 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/1960187

Title:
  [22.04 FEAT] [KRN2013] Support for new IBM Z Hardware in kernel

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

Bug description:
  Feature: Support for new IBM Z Hardware in kernel

  Description:
  Support for new IBM Z Hardware in kernel

  This feature is upstream in kernel 5.15 with
  196e3c6ad1cc ("s390/disassembler: add instructions")
  b3bc7980f4ad ("s390: report more CPU capabilities")

  Request Type: Kernel - Enhancement from IBM
  Upstream Acceptance: Accepted

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


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

[Kernel-packages] [Bug 1975582] Re: [UBUNTU 20.04] rcu stalls with many storage key guests

** Changed in: ubuntu-z-systems
   Importance: Undecided => Medium

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

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

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

Title:
  [UBUNTU 20.04] rcu stalls with many storage key guests

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

Bug description:
  ---Problem Description---
  There can be rcu stalls when running lots of large guests with storage keys:

  [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU
  [1377614.579845] rcu:   18-: (2099 ticks this GP) 
idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 
  [1377614.579895](t=2100 jiffies g=155867385 q=20879)
  [1377614.579898] Task dump for CPU 18:
  [1377614.579899] CPU 1/KVM   R  running task0 1030947 256019 
0x0604
  [1377614.579902] Call Trace:
  [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0)
  [1377614.579918]  [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 
  [1377614.579919]  [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 
  [1377614.579924]  [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 
  [1377614.579926]  [<001f1eceb26c>] update_process_times+0x3c/0x80 
  [1377614.579931]  [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 
  [1377614.579932]  [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 
  [1377614.579933]  [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 
  [1377614.579935]  [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 
  [1377614.579938]  [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 
  [1377614.579942]  [<001f1f4c6d08>] ext_int_handler+0x130/0x134 
  [1377614.579945]  [<001f1ec0af10>] ptep_zap_key+0x40/0x60 

   
  Contact Information = cborn...@de.ibm.com 
   
  ---uname output---
   RELEASE: 5.4.0-90-generic
   VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021

  == Comment: #1 - Christian Borntraeger  - 2022-05-24 
03:59:37 ==
  This is a test patch that might address the rcu stalls.

  == Comment: #2 - Christian Borntraeger  - 2022-05-24 
04:00:22 ==
  This is a 2nd patch that reduces the cost of key setting.

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


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

[Kernel-packages] [Bug 1975582] Re: [UBUNTU 20.04] rcu stalls with many storage key guests

Hi, I have some questions on these patches:
Looks to me that these are not upstream, yet?
At least I couldn't find them in 'linux-next'.
We actually would need to have them upstream first, before we can pick them up.
Is it planned to get them upstream accepted? And if so with which kernel 
version?
And would it make sense tagging these as stable updates?

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

Title:
  [UBUNTU 20.04] rcu stalls with many storage key guests

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

Bug description:
  ---Problem Description---
  There can be rcu stalls when running lots of large guests with storage keys:

  [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU
  [1377614.579845] rcu:   18-: (2099 ticks this GP) 
idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 
  [1377614.579895](t=2100 jiffies g=155867385 q=20879)
  [1377614.579898] Task dump for CPU 18:
  [1377614.579899] CPU 1/KVM   R  running task0 1030947 256019 
0x0604
  [1377614.579902] Call Trace:
  [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0)
  [1377614.579918]  [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 
  [1377614.579919]  [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 
  [1377614.579924]  [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 
  [1377614.579926]  [<001f1eceb26c>] update_process_times+0x3c/0x80 
  [1377614.579931]  [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 
  [1377614.579932]  [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 
  [1377614.579933]  [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 
  [1377614.579935]  [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 
  [1377614.579938]  [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 
  [1377614.579942]  [<001f1f4c6d08>] ext_int_handler+0x130/0x134 
  [1377614.579945]  [<001f1ec0af10>] ptep_zap_key+0x40/0x60 

   
  Contact Information = cborn...@de.ibm.com 
   
  ---uname output---
   RELEASE: 5.4.0-90-generic
   VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021

  == Comment: #1 - Christian Borntraeger  - 2022-05-24 
03:59:37 ==
  This is a test patch that might address the rcu stalls.

  == Comment: #2 - Christian Borntraeger  - 2022-05-24 
04:00:22 ==
  This is a 2nd patch that reduces the cost of key setting.

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


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

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

At least I couldn't find them in 'linux-next'.
We actually would need to have them upstream first, before we can pick them up.

--- Comment From cborn...@de.ibm.com 2022-05-24 07:14 EDT---
(In reply to comment #9)
> Hi, I have some questions on these patches:
> Looks to me that these are not upstream, yet?
> At least I couldn't find them in 'linux-next'.
> We actually would need to have them upstream first, before we can pick them
> up.
> Is it planned to get them upstream accepted? And if so with which kernel
> version?
> And would it make sense tagging these as stable updates?

Not upstream yet and not yet queued. I wrote these patches after looking
at the symptoms. My idea was to let you build a test ppa with these
patches to verify that they really fix the issue. I will then queue them
upstream.

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

Title:
  [UBUNTU 20.04] rcu stalls with many storage key guests

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

Bug description:
  ---Problem Description---
  There can be rcu stalls when running lots of large guests with storage keys:

  [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU
  [1377614.579845] rcu:   18-: (2099 ticks this GP) 
idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 
  [1377614.579895](t=2100 jiffies g=155867385 q=20879)
  [1377614.579898] Task dump for CPU 18:
  [1377614.579899] CPU 1/KVM   R  running task0 1030947 256019 
0x0604
  [1377614.579902] Call Trace:
  [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0)
  [1377614.579918]  [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 
  [1377614.579919]  [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 
  [1377614.579924]  [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 
  [1377614.579926]  [<001f1eceb26c>] update_process_times+0x3c/0x80 
  [1377614.579931]  [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 
  [1377614.579932]  [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 
  [1377614.579933]  [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 
  [1377614.579935]  [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 
  [1377614.579938]  [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 
  [1377614.579942]  [<001f1f4c6d08>] ext_int_handler+0x130/0x134 
  [1377614.579945]  [<001f1ec0af10>] ptep_zap_key+0x40/0x60 

   
  Contact Information = cborn...@de.ibm.com 
   
  ---uname output---
   RELEASE: 5.4.0-90-generic
   VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021

  == Comment: #1 - Christian Borntraeger  - 2022-05-24 
03:59:37 ==
  This is a test patch that might address the rcu stalls.

  == Comment: #2 - Christian Borntraeger  - 2022-05-24 
04:00:22 ==
  This is a 2nd patch that reduces the cost of key setting.

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


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

[Kernel-packages] [Bug 1975582] Re: [UBUNTU 20.04] rcu stalls with many storage key guests

Okay, happy to do that.
I'll kick off a test build in PPA soon.
Will do focal 5.4 and bionic hwe-5.4.

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

Title:
  [UBUNTU 20.04] rcu stalls with many storage key guests

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

Bug description:
  ---Problem Description---
  There can be rcu stalls when running lots of large guests with storage keys:

  [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU
  [1377614.579845] rcu:   18-: (2099 ticks this GP) 
idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 
  [1377614.579895](t=2100 jiffies g=155867385 q=20879)
  [1377614.579898] Task dump for CPU 18:
  [1377614.579899] CPU 1/KVM   R  running task0 1030947 256019 
0x0604
  [1377614.579902] Call Trace:
  [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0)
  [1377614.579918]  [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 
  [1377614.579919]  [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 
  [1377614.579924]  [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 
  [1377614.579926]  [<001f1eceb26c>] update_process_times+0x3c/0x80 
  [1377614.579931]  [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 
  [1377614.579932]  [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 
  [1377614.579933]  [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 
  [1377614.579935]  [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 
  [1377614.579938]  [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 
  [1377614.579942]  [<001f1f4c6d08>] ext_int_handler+0x130/0x134 
  [1377614.579945]  [<001f1ec0af10>] ptep_zap_key+0x40/0x60 

   
  Contact Information = cborn...@de.ibm.com 
   
  ---uname output---
   RELEASE: 5.4.0-90-generic
   VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021

  == Comment: #1 - Christian Borntraeger  - 2022-05-24 
03:59:37 ==
  This is a test patch that might address the rcu stalls.

  == Comment: #2 - Christian Borntraeger  - 2022-05-24 
04:00:22 ==
  This is a 2nd patch that reduces the cost of key setting.

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


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

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

--- Comment From boris.m...@de.ibm.com 2022-05-24 07:34 EDT---
@ Frank: as already mentioned via slack please build a test ppa with these 2 
attached patches, including / on top of the another 2 fixes from bug 198271 / 
launchpad LP#1974017
Thanks a lot.

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

Title:
  [UBUNTU 20.04] rcu stalls with many storage key guests

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

Bug description:
  ---Problem Description---
  There can be rcu stalls when running lots of large guests with storage keys:

  [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU
  [1377614.579845] rcu:   18-: (2099 ticks this GP) 
idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 
  [1377614.579895](t=2100 jiffies g=155867385 q=20879)
  [1377614.579898] Task dump for CPU 18:
  [1377614.579899] CPU 1/KVM   R  running task0 1030947 256019 
0x0604
  [1377614.579902] Call Trace:
  [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0)
  [1377614.579918]  [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 
  [1377614.579919]  [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 
  [1377614.579924]  [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 
  [1377614.579926]  [<001f1eceb26c>] update_process_times+0x3c/0x80 
  [1377614.579931]  [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 
  [1377614.579932]  [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 
  [1377614.579933]  [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 
  [1377614.579935]  [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 
  [1377614.579938]  [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 
  [1377614.579942]  [<001f1f4c6d08>] ext_int_handler+0x130/0x134 
  [1377614.579945]  [<001f1ec0af10>] ptep_zap_key+0x40/0x60 

   
  Contact Information = cborn...@de.ibm.com 
   
  ---uname output---
   RELEASE: 5.4.0-90-generic
   VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021

  == Comment: #1 - Christian Borntraeger  - 2022-05-24 
03:59:37 ==
  This is a test patch that might address the rcu stalls.

  == Comment: #2 - Christian Borntraeger  - 2022-05-24 
04:00:22 ==
  This is a 2nd patch that reduces the cost of key setting.

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


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

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it

[Kernel-packages] [Bug 1975364] Re: Ubuntu 22.04 very long to resume from suspend to ram

apport information

** Tags added: apport-collected

** Description changed:

  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory: I
  can say this because if I type my password plus Enter then wait a long
  time I get my working screen OK.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  fab1681 F pulseaudio
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 22.04
+ HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
+ InstallationDate: Installed on 2013-07-05 (3244 days ago)
+ InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
+ MachineType: Dell Inc. XPS L322X
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
+ ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
+ 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-30-generic N/A
+  linux-backports-modules-5.15.0-30-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3
+ Tags:  jammy
+ Uname: Linux 5.15.0-30-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 08/28/2013
+ dmi.bios.release: 0.1
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A10
+ dmi.board.name: 0PJHXN
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Dell Inc.
+ dmi.chassis.version: 0.1
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
+ dmi.product.family: ChiefRiver System
+ dmi.product.name: XPS L322X
+ dmi.product.sku: XPS L322X
+ dmi.sys.vendor: Dell Inc.
+ modified.conffile..etc.default.apport:
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
+ mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888

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

-- 
You received this bug notification because you are a member o

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to en

[Kernel-packages] [Bug 1975364] PaInfo.txt

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1975364/+attachment/5592605/+files/PaInfo.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/1975364

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   #

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # yo

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enab

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enab

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

apport information

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, o

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   #

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 t

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # yo

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   #

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

apport information

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

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it

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

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1975364/+attachment/5592613/+files/acpidump.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/1975364

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it

[Kernel-packages] [Bug 1975364] Re: Ubuntu 22.04 very long to resume from suspend to ram

Just added apport-collect data after the issue happened again.

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

Title:
  Ubuntu 22.04 very long to resume from suspend to ram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I want to resume my awaken laptop, then login screen comes up but
  it is stuck for roughly 1mn as soon as the password field pops up as I
  hit the Enter key to unlock. The mouse cursor won't move. Key strokes
  won't echo in the password field although they are buffered in memory:
  I can say this because if I type my password plus Enter then wait a
  long time I get my working screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-30-generic 5.15.0-30.31
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1721 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat May 21 10:20:33 2022
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3241 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab1681 F pulseaudio
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  HibernationDevice: RESUME=UUID=eb43d52d-a74d-4460-bece-6abfe97623d7
  InstallationDate: Installed on 2013-07-05 (3244 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. XPS L322X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=c3867e14-cdf3-4837-93cb-5062324fd911 ro acpi_osi=Linux
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  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-30-generic N/A
   linux-backports-modules-5.15.0-30-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  Tags:  jammy
  Uname: Linux 5.15.0-30-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (29 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/28/2013
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:br0.1:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:skuXPSL322X:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.product.sku: XPS L322X
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start fo

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

Vinay, I am running out of idea. Are all affected systems Dell ones? I
am thinking a simple DMI quirk for Dell platforms.

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

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

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

Bug description:
  SRU Justification:

  [IMPACT]

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

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

  according to the hardware partner:

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

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

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

  The hardware partner did some bisection and observed the following:

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

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

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

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

  This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.

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

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

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

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

To manage notifications abo

[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input

It's
"/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00"
on your system.

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

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

Title:
  [Regression] Unable to wake laptop using trackpad input

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to Ubuntu 22.04,
  the dell laptop no longer wakes up using trackpad movement/interaction.

  Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e.,
  Working On:
  Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10.

  NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31
  )

  Just to clarify: Suspend and Resume are working, trackpad is functional 
before and after suspend,
  But,
  Trackpad trigger to wakeup from suspend is not working.

  --

  $ cat /proc/version_signature > version.log
  => Ubuntu 5.15.0-27.28-generic 5.15.30

  -

  $ lsb_release -rd
  =>
  Description:Ubuntu 22.04 LTS
  Release:22.04

  -

  $ apt-cache policy linux-image-generic
  =>
  linux-image-generic:
    Installed: 5.15.0.27.30
    Candidate: 5.15.0.27.30
    Version table:
   *** 5.15.0.27.30 500
  500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 
Packages
  500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages

  -

  What I expected to happen:
  Laptop wakes-up from suspend on touchpad interaction

  -

  What happened:
  Laptop did not wakeup from suspend on touchpad interaction.

  Laptop woke up on the press of power button.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.27.30
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  monkey 5198 F wireplumber
   /dev/snd/controlC1:  monkey 5198 F wireplumber
   /dev/snd/seq:monkey 5195 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri May  6 12:40:22 2022
  InstallationDate: Installed on 2018-10-25 (1288 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 
2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau 
nouveau.modeset=0 vt.handoff=7
  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-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server

2022-05-24 Thread Zhanglei Mao

@Mario, Thanks for those deep and detail analyse for the root cause.

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

Title:
  SATA device hot plug regression on AMD EPYC (Asus) server

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux
  version 5.4.0-109-generic", but it works on earlier version of " Linux
  version 5.4.0-42-generic"

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


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

[Kernel-packages] [Bug 1215155] Re: regression in linux-image-3.8.0-29-generic: ipod shuffle 2g does not mount any more

2022-05-24 Thread Vlad Orlov

** Changed in: linuxmint
   Status: New => Invalid

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

Title:
  regression in linux-image-3.8.0-29-generic: ipod shuffle 2g does not
  mount any more

Status in Linux:
  Unknown
Status in Linux Mint:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  starting with  linux-image-3.8.0-29-generic ipod shuffle 2g could not be 
mounted.
  with 3.8.0-27-generic works OK
  [   23.752494] USB Mass Storage support registered.
  [   24.752744] scsi 4:0:0:0: Direct-Access AppleiPod 2.70 
PQ: 0 ANSI: 2
  [   24.754546] sd 4:0:0:0: Attached scsi generic sg2 type 0
  [   24.755357] sd 4:0:0:0: [sdc] 495616 2048-byte logical blocks: (1.01 
GB/968 MiB)
  [   24.756585] sd 4:0:0:0: [sdc] Write Protect is off
  [   24.756588] sd 4:0:0:0: [sdc] Mode Sense: 64 00 00 08
  [   24.757226] sd 4:0:0:0: [sdc] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
  [   24.758599] sd 4:0:0:0: [sdc] 495616 2048-byte logical blocks: (1.01 
GB/968 MiB)
  [   24.769902]  sdc:
  [   24.771237] sd 4:0:0:0: [sdc] 495616 2048-byte logical blocks: (1.01 
GB/968 MiB)
  [   24.772748] sd 4:0:0:0: [sdc] Attached SCSI removable disk

  
  with 3.8.0-29-generic  I get only 
  [  186.661052] scsi 5:0:0:0: Direct-Access AppleiPod 2.70 
PQ: 0 ANSI: 2
  [  186.662692] sd 5:0:0:0: Attached scsi generic sg2 type 0
  [  186.663501] sd 5:0:0:0: [sdc] 495616 2048-byte logical blocks: (1.01 
GB/968 MiB)
  [  186.664756] sd 5:0:0:0: [sdc] Write Protect is off
  [  186.664765] sd 5:0:0:0: [sdc] Mode Sense: 64 00 00 08
  [  186.666731] sd 5:0:0:0: [sdc] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
  and nothing more, /dev/sdc does not exist

  The same behaviour on T500 and S10-3t. (had to roll back to 3.8.0-27)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-29-generic (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ortyl  2029 F pulseaudio
  Date: Wed Aug 21 23:03:36 2013
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=c6b1277b-2ac7-46e4-b8f3-ce7f93218a25
  InstallationDate: Installed on 2012-09-01 (354 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: LENOVO 20827SG
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=a20647bb-a321-40ad-96f0-47cbe5c02a92 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-27-generic N/A
   linux-backports-modules-3.8.0-27-generic  N/A
   linux-firmware1.106
  SourcePackage: linux
  UpgradeStatus: Upgraded to raring on 2013-04-01 (142 days ago)
  dmi.bios.date: 12/14/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET92WW (3.22 )
  dmi.board.name: 20827SG
  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.modalias: 
dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn20827SG:pvrThinkPadT500:rvnLENOVO:rn20827SG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20827SG
  dmi.product.version: ThinkPad T500
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1974178] Re: Missing vhost_vsock kernel module in 5.15.0

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

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

** Description changed:

+ [Impact]
+ 
+ $ lxc launch images:ubuntu/focal ubuntu --vm
+ 
+ Creating ubuntu
+ Error: Failed instance creation: Failed creating instance record: Instance 
type "virtual-machine" is not supported on this server: vhost_vsock kernel 
module not loaded
+ 
+ [Fix]
+ 
+ Move module vhost_vsock from linux-modules-extra to linux-modules.
+ 
+ [Where Problems Could Occur]
+ 
+ None expected, just moving a module between packages.
+ 
+ [Original Description]
+ 
  Hey All,
  
- I am new to the container, lxc, lxd stuff and  I am at the end of my 
knowledge. 
+ I am new to the container, lxc, lxd stuff and  I am at the end of my 
knowledge.
  I have a fresh setup with a Raspberry PI 4 installed with Ubuntu 22.04 arm64.
- So far everything works fine for containers but I can't get any vm to launch. 
+ So far everything works fine for containers but I can't get any vm to launch.
  
- >     ~  lxc launch images:ubuntu/focal ubuntu --vm 
- > 
+ >     ~  lxc launch images:ubuntu/focal ubuntu --vm
+ >
  > Creating ubuntu
  > Error: Failed instance creation: Failed creating instance record: Instance 
type "virtual-machine" is not supported on this server: vhost_vsock kernel 
module not loaded
  
  Seems like I am missing a kernel module, but I was not able to find or load 
it.
  Already googled for it but was not able to find any matching problem with 
solution.
  
  Additional Information:
  >     ~  uname -r
  > 5.15.0-1005-raspi
  
  >     ~  dpkg -l | grep linux-image
  > ii  linux-image-5.15.0-1005-raspi   5.15.0-1005.5   
arm64Linux kernel image for version 5.15.0 on ARMv8 SMP
  
  >     ~  modprobe vhost_vsock
  >  modprobe: FATAL: Module vhost_vsock not found in directory 
/lib/modules/5.15.0-1005-raspi
  >     ~  lsmod | grep vsock

** Description changed:

  [Impact]
  
- $ lxc launch images:ubuntu/focal ubuntu --vm
+ $ sudo lxc launch images:ubuntu/focal ubuntu --vm
  
  Creating ubuntu
  Error: Failed instance creation: Failed creating instance record: Instance 
type "virtual-machine" is not supported on this server: vhost_vsock kernel 
module not loaded
  
  [Fix]
  
  Move module vhost_vsock from linux-modules-extra to linux-modules.
+ 
+ [Test Case]
+ 
+ See above.
  
  [Where Problems Could Occur]
  
  None expected, just moving a module between packages.
  
  [Original Description]
  
  Hey All,
  
  I am new to the container, lxc, lxd stuff and  I am at the end of my 
knowledge.
  I have a fresh setup with a Raspberry PI 4 installed with Ubuntu 22.04 arm64.
  So far everything works fine for containers but I can't get any vm to launch.
  
  >     ~  lxc launch images:ubuntu/focal ubuntu --vm
  >
  > Creating ubuntu
  > Error: Failed instance creation: Failed creating instance record: Instance 
type "virtual-machine" is not supported on this server: vhost_vsock kernel 
module not loaded
  
  Seems like I am missing a kernel module, but I was not able to find or load 
it.
  Already googled for it but was not able to find any matching problem with 
solution.
  
  Additional Information:
  >     ~  uname -r
  > 5.15.0-1005-raspi
  
  >     ~  dpkg -l | grep linux-image
  > ii  linux-image-5.15.0-1005-raspi   5.15.0-1005.5   
arm64Linux kernel image for version 5.15.0 on ARMv8 SMP
  
  >     ~  modprobe vhost_vsock
  >  modprobe: FATAL: Module vhost_vsock not found in directory 
/lib/modules/5.15.0-1005-raspi
  >     ~  lsmod | grep vsock

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

Title:
  Missing vhost_vsock kernel module in 5.15.0

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi source package in Jammy:
  In Progress

Bug description:
  [Impact]

  $ sudo lxc launch images:ubuntu/focal ubuntu --vm

  Creating ubuntu
  Error: Failed instance creation: Failed creating instance record: Instance 
type "virtual-machine" is not supported on this server: vhost_vsock kernel 
module not loaded

  [Fix]

  Move module vhost_vsock from linux-modules-extra to linux-modules.

  [Test Case]

  See above.

  [Where Problems Could Occur]

  None expected, just moving a module between packages.

  [Original Description]

  Hey All,

  I am new to the container, lxc, lxd stuff and  I am at the end of my 
knowledge.
  I have a fresh setup with a Raspberry PI 4 installed with Ubuntu 22.04 arm64.
  So far everything works fine for containers but I can't get any vm to launch.

  >     ~  lxc launch images:ubuntu/focal ubuntu --vm
  >
  > Creating ubuntu
  > Error: Failed instance creation: Failed creating instance record: Instance 
type "virtual-machine" is not s

[Kernel-packages] [Bug 1975593] [NEW] rename compat to iwlwifi-compat for potential module name collision

Public bug reported:

While we're to build Intel DG2 DKMS in bug 1971712, the newly created
binary package would carry a module named compat, which is also found in
backport-iwlwifi-dkms because they're both generated by linux-backports
project.

To avoid name collision, they shall be renamed as iwlwifi-compat and
i915-compat correspondingly.

** Affects: backport-iwlwifi-dkms (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: backport-iwlwifi-dkms (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: linux-oem-5.17 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: backport-iwlwifi-dkms (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

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

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

** Also affects: backport-iwlwifi-dkms (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: backport-iwlwifi-dkms (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

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

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

Title:
  rename compat to iwlwifi-compat for potential module name collision

Status in backport-iwlwifi-dkms package in Ubuntu:
  New
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms source package in Jammy:
  New
Status in linux-oem-5.17 source package in Jammy:
  New
Status in backport-iwlwifi-dkms source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  While we're to build Intel DG2 DKMS in bug 1971712, the newly created
  binary package would carry a module named compat, which is also found
  in backport-iwlwifi-dkms because they're both generated by linux-
  backports project.

  To avoid name collision, they shall be renamed as iwlwifi-compat and
  i915-compat correspondingly.

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


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

[Kernel-packages] [Bug 1975592] [NEW] Enable Nezha board

2022-05-24 Thread Dimitri John Ledkov

Public bug reported:

Enable Nezha board

Apply relevant patches to linux-riscv-5.17 kernel to enable nezha kernel
flavour.

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

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

Title:
  Enable Nezha board

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  Enable Nezha board

  Apply relevant patches to linux-riscv-5.17 kernel to enable nezha
  kernel flavour.

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


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

[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input

@kaihengfeng There is no "wakeup" file in
"/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00"



** Attachment added: "Output of: $ sudo tree 
/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00 > 
fs-tree.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+attachment/5592623/+files/fs-tree.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/1971933

Title:
  [Regression] Unable to wake laptop using trackpad input

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to Ubuntu 22.04,
  the dell laptop no longer wakes up using trackpad movement/interaction.

  Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e.,
  Working On:
  Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10.

  NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31
  )

  Just to clarify: Suspend and Resume are working, trackpad is functional 
before and after suspend,
  But,
  Trackpad trigger to wakeup from suspend is not working.

  --

  $ cat /proc/version_signature > version.log
  => Ubuntu 5.15.0-27.28-generic 5.15.30

  -

  $ lsb_release -rd
  =>
  Description:Ubuntu 22.04 LTS
  Release:22.04

  -

  $ apt-cache policy linux-image-generic
  =>
  linux-image-generic:
    Installed: 5.15.0.27.30
    Candidate: 5.15.0.27.30
    Version table:
   *** 5.15.0.27.30 500
  500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 
Packages
  500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages

  -

  What I expected to happen:
  Laptop wakes-up from suspend on touchpad interaction

  -

  What happened:
  Laptop did not wakeup from suspend on touchpad interaction.

  Laptop woke up on the press of power button.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.27.30
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  monkey 5198 F wireplumber
   /dev/snd/controlC1:  monkey 5198 F wireplumber
   /dev/snd/seq:monkey 5195 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri May  6 12:40:22 2022
  InstallationDate: Installed on 2018-10-25 (1288 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 
2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau 
nouveau.modeset=0 vt.handoff=7
  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-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1975593] Re: rename DKMS compat module for potential name collision

** Summary changed:

- rename compat to iwlwifi-compat for potential module name collision
+ rename DKMS compat module for potential name collision

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

Title:
  rename DKMS compat module for potential name collision

Status in backport-iwlwifi-dkms package in Ubuntu:
  New
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms source package in Jammy:
  New
Status in linux-oem-5.17 source package in Jammy:
  New
Status in backport-iwlwifi-dkms source package in Kinetic:
  New
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  While we're to build Intel DG2 DKMS in bug 1971712, the newly created
  binary package would carry a module named compat, which is also found
  in backport-iwlwifi-dkms because they're both generated by linux-
  backports project.

  To avoid name collision, they shall be renamed as iwlwifi-compat and
  i915-compat correspondingly.

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


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

[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input

@kaihengfeng There is no "wakeup" file in
/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00

I'm attaching the output of  sudo ls  --recursive
/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00
> fs-ls.txt


"tree" command had weird characters in output file as rendered on bug page.

** Attachment added: "Output of: $ sudo ls  --recursive 
/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00 > 
fs-ls*.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+attachment/5592624/+files/fs-ls.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/1971933

Title:
  [Regression] Unable to wake laptop using trackpad input

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to Ubuntu 22.04,
  the dell laptop no longer wakes up using trackpad movement/interaction.

  Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e.,
  Working On:
  Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10.

  NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31
  )

  Just to clarify: Suspend and Resume are working, trackpad is functional 
before and after suspend,
  But,
  Trackpad trigger to wakeup from suspend is not working.

  --

  $ cat /proc/version_signature > version.log
  => Ubuntu 5.15.0-27.28-generic 5.15.30

  -

  $ lsb_release -rd
  =>
  Description:Ubuntu 22.04 LTS
  Release:22.04

  -

  $ apt-cache policy linux-image-generic
  =>
  linux-image-generic:
    Installed: 5.15.0.27.30
    Candidate: 5.15.0.27.30
    Version table:
   *** 5.15.0.27.30 500
  500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 
Packages
  500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages

  -

  What I expected to happen:
  Laptop wakes-up from suspend on touchpad interaction

  -

  What happened:
  Laptop did not wakeup from suspend on touchpad interaction.

  Laptop woke up on the press of power button.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.27.30
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  monkey 5198 F wireplumber
   /dev/snd/controlC1:  monkey 5198 F wireplumber
   /dev/snd/seq:monkey 5195 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri May  6 12:40:22 2022
  InstallationDate: Installed on 2018-10-25 (1288 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 
2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau 
nouveau.modeset=0 vt.handoff=7
  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-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1975582] Re: [UBUNTU 20.04] rcu stalls with many storage key guests

A focal 5.4 and a bionic hwe-5.4 kernel are now build for testing at PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1975582
respectively:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1975582/+packages

They both include (top-most commits):
"s390/pgtable: use non-quiescing sske for KVM switch to keyed"
"s390/gmap: voluntarily schedule during key setting"
"KVM: s390: vsie/gmap: reduce gmap_rmap overhead"
"NFS: Fix up nfs_ctx_key_to_expire()"

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

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

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

Title:
  [UBUNTU 20.04] rcu stalls with many storage key guests

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  ---Problem Description---
  There can be rcu stalls when running lots of large guests with storage keys:

  [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU
  [1377614.579845] rcu:   18-: (2099 ticks this GP) 
idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 
  [1377614.579895](t=2100 jiffies g=155867385 q=20879)
  [1377614.579898] Task dump for CPU 18:
  [1377614.579899] CPU 1/KVM   R  running task0 1030947 256019 
0x0604
  [1377614.579902] Call Trace:
  [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0)
  [1377614.579918]  [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 
  [1377614.579919]  [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 
  [1377614.579924]  [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 
  [1377614.579926]  [<001f1eceb26c>] update_process_times+0x3c/0x80 
  [1377614.579931]  [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 
  [1377614.579932]  [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 
  [1377614.579933]  [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 
  [1377614.579935]  [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 
  [1377614.579938]  [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 
  [1377614.579942]  [<001f1f4c6d08>] ext_int_handler+0x130/0x134 
  [1377614.579945]  [<001f1ec0af10>] ptep_zap_key+0x40/0x60 

   
  Contact Information = cborn...@de.ibm.com 
   
  ---uname output---
   RELEASE: 5.4.0-90-generic
   VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021

  == Comment: #1 - Christian Borntraeger  - 2022-05-24 
03:59:37 ==
  This is a test patch that might address the rcu stalls.

  == Comment: #2 - Christian Borntraeger  - 2022-05-24 
04:00:22 ==
  This is a 2nd patch that reduces the cost of key setting.

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


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

[Kernel-packages] [Bug 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)

2022-05-24 Thread Sebastien Bacher

Note that in kinetic we are switching to pipewire, unsure if that has
the same issue

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

Title:
  [nouveau] Weird colors after startup (Ubuntu 22.04)

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [Workaround/Fix]

  1. When starting the Ubuntu live image, select the option 'Ubuntu
  (safe graphics)' from the boot menu.

  2. During installation be sure to select the third-party software
  option checkbox in order to get the right Nvidia driver installed.

  [Original Description]

  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7C56
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  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.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):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-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

2022-05-24 Thread Kevin Peter Gade

Hello.
I have tried to follow above instructions carefully, recompiling my own file. 
However for me its not working, unfortunately battery is still not recognized. 

I followed these steps:

1) install acpica-tools
sudo apt-get install acpica-tools

2) Grab the DSDT of your device
sudo cat /sys/firmware/acpi/tables/DSDT > dsdt.dat

3) Decompile the dsdt.dat
sudo iasl -d dsdt.dat

4) Open the dsdt.dsl with whatever editor tickles your fancy
sudo xed dsdt.dsl

5) Delete everything with a * in front, first line should be "DefinitionBlock"
(For me that include Firmware Error (ACPI) in line 1 and 2 - if that could 
matter:
Could not resolve [^GFX0.CLID], AE_NOT_FOUND (20190509/dswload-388)
Could not resolve [^GFX0.CLID], AE_NOT_FOUND (20190509/dswload2-369)

6) Raise the last number in Definition Block by one
e.g.:
DefinitionBlock ("", "DSDT", 2, "FUJ ", "FJNBB6D ", 0x010C)
   ↓
DefinitionBlock ("", "DSDT", 2, "FUJ ", "FJNBB6D ", 0x010C0001)

7) Search for the string "OperationRegion (ERAM"
for me it was at line 18751; your mileage may vary

8) Replace the entire line with this one:
OperationRegion (ERAM, EmbeddedControl, Zero, 0x0100)

(I had OperationRegion (ERAM, SystemMemory, 0xFE508300, 0x0100) to begin
with)

9) Save and Exit

10) Recompile the dsdt.dsl (Note: This WILL show loads of warnings and 
optimizations
This will give you a dsdt.aml that should work.

I did that with: sudo iasl -ta dsdt.dsl and got the aml file just with
warnings.

11) Proceed as above

sudo cp dsdt.aml /boot/
sudo cp 01_acpi /etc/grub.d/
chmod 755 01_acpi
sudo update-grub
reboot

Still just the same :/
Can anyone point me in the right direction?

PS. BIOS v. 1.12 (freshly update through Windows, Fujitsu DeskUpdate).

Br. Kevin

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better result. 
What is the problem here, and how can I fix it?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas  945 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-12-31 (4 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic 
root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-22-generic N/A
   linux-backports-modules-5.13.0-22-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish
  Uname: Linux 5.13.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/22/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 1.12
  dmi.board.name: FJNBB6D
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: EQAB073106
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK A3510
  dmi.product.sku: SK00
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

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


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

[Kernel-packages] [Bug 1975593] Re: rename DKMS compat module for potential name collision

PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1975573 (shared
with bug 1975573)

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

Title:
  rename DKMS compat module for potential name collision

Status in backport-iwlwifi-dkms package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  New
Status in backport-iwlwifi-dkms source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  While we're to build Intel DG2 DKMS in bug 1971712, the newly created
  binary package would carry a module named compat, which is also found
  in backport-iwlwifi-dkms because they're both generated by linux-
  backports project.

  To avoid name collision, they shall be renamed as iwlwifi-compat and
  i915-compat correspondingly.

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


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

[Kernel-packages] [Bug 1970392] Re: 22.04 USB devices do not work after sleep on Dell XPS 13 9370

2022-05-24 Thread Aaron Whitehouse

Thanks Kai-Heng.

I have updated this and will keep you posted:
$ sudo dmidecode -s bios-version
1.19.0
$ sudo dmidecode -s bios-release-date
03/22/2022


Devices that have been updated successfully:
 • System Firmware (1.12.1 → 1.19.0)

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

Title:
  22.04 USB devices do not work after sleep on Dell XPS 13 9370

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9370 that came with Ubuntu preinstalled. I have
  just completed a fresh install of 22.04 on it.

  When I suspend the laptop, the USB devices that were plugged in when I
  suspended do not work. Specifically, I had an Ethernet adapter and a
  USB-C monitor with a keyboard attached through it. The monitor display
  works as expected, but neither the keyboard nor the Ethernet adapter
  work after suspending.

  Interestingly, I can move the Ethernet adapter to the remaining USB-C
  port and it works correctly. Moving it back afterwards, it still does
  not work.

  Please let me know if there is anything more I can do to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aaron-work  35648 F pulseaudio
   /dev/snd/controlC0:  aaron-work  35648 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 10:36:09 2022
  InstallationDate: Installed on 2022-04-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:br1.12:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input

@kaihengfeng The above "tree
/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00"
command output in html format.


** Attachment added: "sudo tree -C -H https://launchpadlibrarian.net/602970382/ 
/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00 > 
tree-html.html"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+attachment/5592632/+files/tree-html.html

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

Title:
  [Regression] Unable to wake laptop using trackpad input

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to Ubuntu 22.04,
  the dell laptop no longer wakes up using trackpad movement/interaction.

  Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e.,
  Working On:
  Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10.

  NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31
  )

  Just to clarify: Suspend and Resume are working, trackpad is functional 
before and after suspend,
  But,
  Trackpad trigger to wakeup from suspend is not working.

  --

  $ cat /proc/version_signature > version.log
  => Ubuntu 5.15.0-27.28-generic 5.15.30

  -

  $ lsb_release -rd
  =>
  Description:Ubuntu 22.04 LTS
  Release:22.04

  -

  $ apt-cache policy linux-image-generic
  =>
  linux-image-generic:
    Installed: 5.15.0.27.30
    Candidate: 5.15.0.27.30
    Version table:
   *** 5.15.0.27.30 500
  500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 
Packages
  500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages

  -

  What I expected to happen:
  Laptop wakes-up from suspend on touchpad interaction

  -

  What happened:
  Laptop did not wakeup from suspend on touchpad interaction.

  Laptop woke up on the press of power button.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.27.30
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  monkey 5198 F wireplumber
   /dev/snd/controlC1:  monkey 5198 F wireplumber
   /dev/snd/seq:monkey 5195 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri May  6 12:40:22 2022
  InstallationDate: Installed on 2018-10-25 (1288 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 
2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau 
nouveau.modeset=0 vt.handoff=7
  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-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1975599] [NEW] jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-05-24)

Public bug reported:

Upstream raspberrypi patchset 2022-05-24

  Ported from the following raspberrypi branch:
rpi-5.15.y
  from https://github.com/raspberrypi/linux.git

overlays: add RV8803 RTC overlay to the generic ARM RTC device tree
configs: add RV8803 RTC module to Raspberry Pi board defconfigs
media: imx296: Add the link frequency control
media: imx296: Set gain delay to 1 frame
media: imx296: Adjust exposure limits on vblank changes
media: imx296: Add horizontal and vertical flips support
media: imx296: Only advertise the full resolution mode
media: imx296: Add standby and stream on/off delays
media: imx296: Fix Bayer order
configs: Enable the IMX296 device module in platform defconfig
overlays: Add imx296 overlay
media: i2c: IMX296 camera sensor driver
dt-bindings: media: i2c: Add IMX296 CMOS sensor binding
drm/vc4: Move pixel doubling from Pixelvalve to HDMI block
drm/vc4: Correct HDMI timing registers for interlaced modes
drm/vc4: Add MISC_CONTROL register for vc4.
drm/vc4: Add HDMI format detection registers to register list
vc04_services: bcm2835-codec: Add support for V4L2_PIX_FMT_NV12_COL128
vc04_services: vchiq-mmal: Add defines for mmal_es_format flags
configs: Regenerate defconfigs
mmc: block: Don't do single-sector reads during recovery
overlays: Add gpio-hog overlay
drm/atomic: If margins are updated, update all planes.
drm/vc4_hdmi: Force a modeset when Broadcast RGB setting changes
dtoverlays: Fix incorrect property name for display rotation
drm/vc4: Warn if some v3d code is run on BCM2711
drm/vc4: crtc: Don't call into BO Handling on Async Page-Flips on BCM2711
drm/vc4: crtc: Move the BO Handling out of Common Page-Flip Handler
drm/vc4: crtc: Move the BO handling out of common page-flip callback
drm/vc4: crtc: Use an union to store the page flip callback
drm/vc4: drv: Skip BO Backend Initialization on BCM2711
drm/vc4: plane: Register a different drm_plane_helper_funcs on BCM2711
drm/vc4: kms: Register a different drm_mode_config_funcs on BCM2711
drm/vc4: drv: Register a different driver on BCM2711
drm/vc4: bo: Split out Dumb buffers fixup
drm/vc4: bo: Rename vc4_dumb_create
drm/vc4: Consolidate Hardware Revision Check
drm/vc4: plane: Prevent async update if we don't have a dlist
clk: Add locking to clk_get_rate_range
overlays: Remove other leading zeroes from node addresses
SQUASH: overlays: arducam-pivariety: Strip leading zero
dtoverlays: Add i2c-fan overlay
configs: Enable the EMC2305 fan controller driver
docs: hwmon: add emc2305.rst to docs
hwmon: emc2305: fixups for driver submitted to mailing lists
hwmon: (emc2305) add support for EMC2301/2/3/5 RPM-based PWM Fan Speed 
Controller.
dtbindings: Fixup microchip,emc2305.yaml bindings
dt-bindings: hwmon: add microchip,emc2305.yaml dt binding description.
thermal: broadcom: Use dev_err_probe to suppress defer errors
overlays: Add arducam-pivariety-overlay.dts
configs: Add CONFIG_VIDEO_ARDUCAM_PIVARIETY=m
media: i2c: Add driver of Arducam Pivariety series camera
media: dt-bindings: media: i2c: Add Arducam Pivariety Series CMOS sensor binding
dt-bindings: vendor-prefixes: Add Arducam
configs: Restore settings lost since 5.10
configs: Enable DM_WRITECACHE module on BCM2711
configs: Add CONFIG_EEPROM_AT25=m
staging: vchiq_arm: Add log_level module params
config: Update bcmrpi3_defconfig
Revert "fbdev: Hot-unplug firmware fb devices on forced removal"
Revert "fbdev: Fix unregistering of framebuffers without device"
drm/vc4_kms: Protect hvs dereference on fkms
ARM: dts: bcm2835: Switch HSM clock to firmware
overlays: Fix pitft28/35-resistive rotate params
ARM: dts: Add i2c0mux node to Model B rev 1
overlays: Add "drm" parameter to pitft28-resistive
tpm_tis_spi_main: Force probe routine to run synchronously with driver and 
device registration when IMA is enabled
clk-bcm2835: use subsys_initcall for the clock driver when IMA is enabled
rpivid: Use clk_get_max_rate()
drm/vc4: kms: Use maximum FIFO load for the HVS clock rate
drm/vc4: Make sure we don't end up with a core clock too high
drm/vc4: kms: Warn if clk_set_min_rate fails
drm/vc4: hdmi: Rework hdmi_enable_4kp60 detection
clk: tests: Add missing test case for ranges
clk: tests: Add some tests for clk_get_rate_range()
clk: Add clk_get_rate_range
Revert "clk: Introduce a clock request API"
Revert "clk: requests: Ignore if the pointer is null"
Revert "clk: requests: Dereference the request pointer after the check"
Revert "rpivid: Switch to new clock api"
Revert "bcm2835-unicam: Switch to new clock api"
Revert "drm/vc4: hdmi: Convert to the new clock request API"
Revert "drm/vc4: Increase the core clock based on HVS load"
Revert "drm/vc4: kms: Move clock request to our HVS state"
clk: bcm: rpi: Run some clocks at the minimum rate allowed
clk: bcm: rpi: Set a default minimum rate
clk: bcm: rpi: Add variant structure
clk: Test the clock pointer in clk_hw_get_name()
clk: Zero the clk_rate_request structure
clk: Stop forwarding clk_rate_requests to the parent
clk: Introduce clk_core_ha

[Kernel-packages] [Bug 1975593] Re: rename DKMS compat module for potential name collision

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

** Changed in: backport-iwlwifi-dkms (Ubuntu Kinetic)
   Status: New => In Progress

** Changed in: backport-iwlwifi-dkms (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: backport-iwlwifi-dkms (Ubuntu Kinetic)
   Importance: Undecided => High

** Changed in: backport-iwlwifi-dkms (Ubuntu Jammy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: backport-iwlwifi-dkms (Ubuntu Kinetic)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  rename DKMS compat module for potential name collision

Status in backport-iwlwifi-dkms package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in backport-iwlwifi-dkms source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  While we're to build Intel DG2 DKMS in bug 1971712, the newly created
  binary package would carry a module named compat, which is also found
  in backport-iwlwifi-dkms because they're both generated by linux-
  backports project.

  To avoid name collision, they shall be renamed as iwlwifi-compat and
  i915-compat correspondingly.

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


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

[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input

@kaihengfeng The above "tree
/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00"
command output in html format.

** Attachment added: "sudo tree -C -H 
/sys/devices/pci\:00/\:00\:15.1/i2c_designware.1/i2c-2/i2c-DLL0798\:00/ 
/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00 > 
tree-html.html"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933/+attachment/5592633/+files/tree-html.html

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

Title:
  [Regression] Unable to wake laptop using trackpad input

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to Ubuntu 22.04,
  the dell laptop no longer wakes up using trackpad movement/interaction.

  Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e.,
  Working On:
  Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10.

  NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31
  )

  Just to clarify: Suspend and Resume are working, trackpad is functional 
before and after suspend,
  But,
  Trackpad trigger to wakeup from suspend is not working.

  --

  $ cat /proc/version_signature > version.log
  => Ubuntu 5.15.0-27.28-generic 5.15.30

  -

  $ lsb_release -rd
  =>
  Description:Ubuntu 22.04 LTS
  Release:22.04

  -

  $ apt-cache policy linux-image-generic
  =>
  linux-image-generic:
    Installed: 5.15.0.27.30
    Candidate: 5.15.0.27.30
    Version table:
   *** 5.15.0.27.30 500
  500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 
Packages
  500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages

  -

  What I expected to happen:
  Laptop wakes-up from suspend on touchpad interaction

  -

  What happened:
  Laptop did not wakeup from suspend on touchpad interaction.

  Laptop woke up on the press of power button.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.27.30
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  monkey 5198 F wireplumber
   /dev/snd/controlC1:  monkey 5198 F wireplumber
   /dev/snd/seq:monkey 5195 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri May  6 12:40:22 2022
  InstallationDate: Installed on 2018-10-25 (1288 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 
2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau 
nouveau.modeset=0 vt.handoff=7
  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-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic

Hello Ian, or anyone else affected,

Accepted nvidia-graphics-drivers-510-server into jammy-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-510-server/510.73.08-0ubuntu0.22.04.1 in a few hours, and then
in the -proposed repository.

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

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

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

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

** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-jammy

** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Kinetic)
   Status: Confirmed => Fix Committed

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

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  In Progress
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  In Progress
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  In Progress
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

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


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

[Kernel-packages] [Bug 1975593] Re: rename DKMS compat module for potential name collision

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2022-May/130574.html 
(linux-oem-5.17)

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

Title:
  rename DKMS compat module for potential name collision

Status in backport-iwlwifi-dkms package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  In Progress
Status in backport-iwlwifi-dkms source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  While we're to build Intel DG2 DKMS in bug 1971712, the newly created
  binary package would carry a module named compat, which is also found
  in backport-iwlwifi-dkms because they're both generated by linux-
  backports project.

  To avoid name collision, they shall be renamed as iwlwifi-compat and
  i915-compat correspondingly.

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


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

[Kernel-packages] [Bug 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic

Hello Ian, or anyone else affected,

Accepted nvidia-graphics-drivers-510-server into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-510-server/510.73.08-0ubuntu0.20.04.1 in a few hours, and then
in the -proposed repository.

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

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

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

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

** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  In Progress
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  In Progress
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

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


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

[Kernel-packages] [Bug 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic

Hello Ian, or anyone else affected,

Accepted nvidia-graphics-drivers-510-server into impish-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-510-server/510.73.08-0ubuntu0.21.10.1 in a few hours, and then
in the -proposed repository.

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

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

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

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

** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-impish

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

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  In Progress
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

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


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

[Kernel-packages] [Bug 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic

Hello Ian, or anyone else affected,

Accepted nvidia-graphics-drivers-510-server into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-510-server/510.73.08-0ubuntu0.18.04.1 in a few hours, and then
in the -proposed repository.

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

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

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

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

** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

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


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

[Kernel-packages] [Bug 1975460] Re: ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card does not work: Intel Corporation Wireless 7260

2022-05-24 Thread SZ

** Summary changed:

- iwlwifi cannot load firmware, wifi card does not work Intel Corporation 
Wireless 7260
+ ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card does not 
work: Intel Corporation Wireless 7260

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

Title:
  ubuntu 22.04 kernel 5.15.0.x iwlwifi cannot load firmware, wifi card
  does not work: Intel Corporation Wireless 7260

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

Bug description:
  With ubuntu 20.04, it worked.
  After upgrading to 22.04, stopped working.
  I have 2 pcs. of HP zbook G2, they both have the same error after upgrade.
  Can't work!!
  Booting back to old linux kernel 5.13.x wifi works again!
  No windows installed, not a dual boot.

  I have other older hp laptop which has a different wifi card, that
  works well with the new kernel.

  Please fix this bug.
  Thank you!

  Full ubuntu-bug report has been sent also.

  Error msg:
  [   23.227024] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0 
7260-17.ucode op_mode iwlmvm
  [   23.309876] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless N 
7260, REV=0x144
  [   28.356103] iwlwifi :3d:00.0: Failed to load firmware chunk!
  [   28.356123] iwlwifi :3d:00.0: iwlwifi transaction failed, dumping 
registers
  [   28.356140] iwlwifi :3d:00.0: iwlwifi device config registers:
  [   28.356415] iwlwifi :3d:00.0: : 08b18086 00100406 0280006b 
0010 d014   
  [   28.356437] iwlwifi :3d:00.0: 0020:    
c0608086  00c8  0100
  [   28.356459] iwlwifi :3d:00.0: 0040: 00020010 10008ec0 00130c10 
0106ec11 101100ca   
  [   28.356480] iwlwifi :3d:00.0: 0060:  00080812 0405 
 00010001   
  [   28.356523] iwlwifi :3d:00.0: 0080:    
    
  [   28.356566] iwlwifi :3d:00.0: 00a0:    
    
  [   28.356607] iwlwifi :3d:00.0: 00c0:   c823d001 
0d00 00814005 fee003f8  
  [   28.356649] iwlwifi :3d:00.0: 00e0:    
    
  [   28.356691] iwlwifi :3d:00.0: 0100: 14010001 4000  
00462031 2000 2000 000e 
  [   28.356732] iwlwifi :3d:00.0: 0120:    
    
  [   28.356774] iwlwifi :3d:00.0: 0140: 14c10003 ff64778d e8b1fcff 
15410018 08460846 0001000b 0141cafe 00f01e1f
  [   28.356815] iwlwifi :3d:00.0: iwlwifi device memory mapped registers:
  [   28.356891] iwlwifi :3d:00.0: : 00489204 8040 2000 
0800    
  [   28.356933] iwlwifi :3d:00.0: 0020: 0009 080003c5 0144 
 8000 803a 80008040 00080046
  [   28.356978] iwlwifi :3d:00.0: iwlwifi device AER capability structure:
  [   28.357034] iwlwifi :3d:00.0: : 14010001 4000  
00462031 2000 2000 000e 
  [   28.357075] iwlwifi :3d:00.0: 0020:   
  [   28.357100] iwlwifi :3d:00.0: iwlwifi parent port (:3c:01.0) 
config registers:
  [   28.357274] iwlwifi :3c:01.0: : 240412d8 00180407 06040005 
00010010   003d3d3c 01f1
  [   28.357316] iwlwifi :3c:01.0: 0020: d010d010 0001fff1  
  0040  0002010a
  [   28.357357] iwlwifi :3c:01.0: 0040: ffc34c01 0008  
00816405 fee002d8   
  [   28.357399] iwlwifi :3c:01.0: 0060:  0034b009 04001060 
04000800 8000 0a730100 76b50080 21901d27
  [   28.357440] iwlwifi :3c:01.0: 0080: 000f  3308 
00790010 8000 116b 000f0022 
  [   28.357482] iwlwifi :3c:01.0: 00a0:    
 c00d 240412d8  
  [   28.357524] iwlwifi :3c:01.0: 00c0: 00620010 8001 0010 
01203c11 10110042  014803c0 
  [   28.357565] iwlwifi :3c:01.0: 00e0:  00040800 0400 
 00010042   
  [   28.357607] iwlwifi :3c:01.0: 0100: 14010001   
00062011  2000 00a0 
  [   28.357648] iwlwifi :3c:01.0: 0120:    
    
  [   28.357690] iwlwifi :3c:01.0: 0140: 20c10002 0800  
 047f0009 8001  
  [   28.357739] iwlwifi :3c:01.0: 0160:  000

[Kernel-packages] [Bug 1975616] [NEW] [UBUNTU 20.04] Several "failed assertion in udev" messages causing unexpected errors in the system

You have been subscribed to a public bug:

---Problem Description---
Several " failed assertion in udev" messages  causing unexpected errors in the 
system causing multiple concurrent dumps to be generated.
This system is a s390x cloud appliance LPAR hosting multiple VMS
This issue is suspected to be seen ,when the VMs(Virtual Server Instance) is 
being spawned and during its  attempt to rename a network interface derived 
from one  SRIOV interface from Mellanox CX5 NIC. 
We see multiple of such messages from journalctl as below  that caused the 
concurrent dump. The pattern always repeats while renaming a virtual function 
based interface. 

We would like to know , what's causing the assertion and subsequent dumps 
Feel free to let us know for dump information( as this is a customer machine, 
as i need to follow a process to get the same )


Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.208754] I6 NDP3 578b7bb 
0024/361-s04 IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd 
SRC=fe80::::0210:6fff:fe24:e58c 
DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=UDP SPT=52245 DPT=9901 LEN=512
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213811] IPv4: martian 
source 192.168.255.255 from 192.168.104.119, on dev IMGMT.53
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213813] ll header: 
: ff ff ff ff ff ff 00 10 6f 24 e5 8c 08 00
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213911] IPv4: martian 
source 192.168.255.255 from 192.168.104.119, on dev IMGMT.53
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213913] ll header: 
: ff ff ff ff ff ff 00 10 6f 24 e5 8c 08 00
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 systemd-udevd[1716040]: Using default 
interface naming scheme 'v245'.
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: mlx5_core 0001:00:06.7 p0v53: 
renamed from if02089C284C2C
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 IDP 578b7bb 0024/361-s04 
IN=vlan1.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd:60:00:00:00 
SRC=fe80::::0210:6fff:fe24:e58c 
DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=UDP SPT=52245 DPT=9901 LEN=512
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 NDP3 578b7bb 0024/361-s04 
IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd 
SRC=fe80::::0210:6fff:fe24:e58c 
DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=UDP SPT=52245 DPT=9901 LEN=512
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 NDP3 578b7bb 0024/361-s04 
IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd 
SRC=fe80::::0210:6fff:fe24:e58c 
DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=UDP SPT=52245 DPT=9901 LEN=512
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: IPv4: martian source 
192.168.255.255 from 192.168.104.119, on dev IMGMT.53
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: ll header: : ff ff ff ff 
ff ff 00 10 6f 24 e5 8c 08 00
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: IPv4: martian source 
192.168.255.255 from 192.168.104.119, on dev IMGMT.53
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: ll header: : ff ff ff ff 
ff ff 00 10 6f 24 e5 8c 08 00
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 NetworkManager[19870]:   
[1646290398.8433] device (if02089C284C2C): interface index 208 renamed iface 
from 'if02089C284C2C' to 'p0v53'
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[1716040]: ethtool: 
autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[1716040]: Assertion 'size 
> 0' failed at src/udev/udev-event.c:449, function udev_event_apply_format(). 
Aborting.
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[19533]: Worker [1716040] 
terminated by signal 6 (ABRT)
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[19533]: p0v53: Worker 
[1716040] failed
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 /usr/sbin/fpcStealConsole[19295]: 
/usr/sbin/event-daemonCoreDump.sh Wrote 
/var/crash/userfiles/core.systemd-udevd.1716040.6
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 /usr/sbin/fpcStealConsole[19295]: 
/usr/sbin/event-daemonCoreDump.sh: Sent log 2A5A0092: Process 
systemd-udevd.1716040 core dumped (6).
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 kernel: I4 IDP2 578b7bb 0024/361-s04 
IN=vlan1.53 OUT= MAC=02:cc:ef:80:d1:11:52:70:89:51:de:08:08:00:45:00:00:45 
SRC=192.168.81.0 DST=192.168.105.8 LEN=69 TOS=0x00 PREC=0x00 TTL=63 ID=60189 DF 
PROTO=UDP SPT=53 DPT=62817 LEN=49


It is also interesting to see some mlx cmd request is being issues by kernel 
being shown as cmd failure much before the interface renaming calls ..We don't 
know whether this has any impact..but mentioning it here 
Mar 03 06:37:17.882760 tok1-qz1-sr5-rk361-s04 kernel: net_ratelimit: 280 
callbacks suppressed
Mar 03 06:37:17.882808 tok1-qz1-sr5-rk361-s04 kernel: IPv4: ma

[Kernel-packages] [Bug 1975616] [NEW] [UBUNTU 20.04] Several "failed assertion in udev" messages causing unexpected errors in the system

Public bug reported:

---Problem Description---
Several " failed assertion in udev" messages  causing unexpected errors in the 
system causing multiple concurrent dumps to be generated.
This system is a s390x cloud appliance LPAR hosting multiple VMS
This issue is suspected to be seen ,when the VMs(Virtual Server Instance) is 
being spawned and during its  attempt to rename a network interface derived 
from one  SRIOV interface from Mellanox CX5 NIC. 
We see multiple of such messages from journalctl as below  that caused the 
concurrent dump. The pattern always repeats while renaming a virtual function 
based interface. 

We would like to know , what's causing the assertion and subsequent dumps 
Feel free to let us know for dump information( as this is a customer machine, 
as i need to follow a process to get the same )


Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.208754] I6 NDP3 578b7bb 
0024/361-s04 IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd 
SRC=fe80::::0210:6fff:fe24:e58c 
DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=UDP SPT=52245 DPT=9901 LEN=512
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213811] IPv4: martian 
source 192.168.255.255 from 192.168.104.119, on dev IMGMT.53
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213813] ll header: 
: ff ff ff ff ff ff 00 10 6f 24 e5 8c 08 00
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213911] IPv4: martian 
source 192.168.255.255 from 192.168.104.119, on dev IMGMT.53
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: [6545462.213913] ll header: 
: ff ff ff ff ff ff 00 10 6f 24 e5 8c 08 00
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 systemd-udevd[1716040]: Using default 
interface naming scheme 'v245'.
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: mlx5_core 0001:00:06.7 p0v53: 
renamed from if02089C284C2C
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 IDP 578b7bb 0024/361-s04 
IN=vlan1.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd:60:00:00:00 
SRC=fe80::::0210:6fff:fe24:e58c 
DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=UDP SPT=52245 DPT=9901 LEN=512
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 NDP3 578b7bb 0024/361-s04 
IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd 
SRC=fe80::::0210:6fff:fe24:e58c 
DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=UDP SPT=52245 DPT=9901 LEN=512
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: I6 NDP3 578b7bb 0024/361-s04 
IN=IMGMT.53 OUT= MAC=33:33:00:00:00:01:00:10:6f:24:e5:8c:86:dd 
SRC=fe80::::0210:6fff:fe24:e58c 
DST=ff02:::::::0001 LEN=552 TC=0 HOPLIMIT=1 FLOWLBL=0 
PROTO=UDP SPT=52245 DPT=9901 LEN=512
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: IPv4: martian source 
192.168.255.255 from 192.168.104.119, on dev IMGMT.53
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: ll header: : ff ff ff ff 
ff ff 00 10 6f 24 e5 8c 08 00
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: IPv4: martian source 
192.168.255.255 from 192.168.104.119, on dev IMGMT.53
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 kernel: ll header: : ff ff ff ff 
ff ff 00 10 6f 24 e5 8c 08 00
Mar  3 06:53:18 tok1-qz1-sr5-rk361-s04 NetworkManager[19870]:   
[1646290398.8433] device (if02089C284C2C): interface index 208 renamed iface 
from 'if02089C284C2C' to 'p0v53'
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[1716040]: ethtool: 
autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[1716040]: Assertion 'size 
> 0' failed at src/udev/udev-event.c:449, function udev_event_apply_format(). 
Aborting.
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[19533]: Worker [1716040] 
terminated by signal 6 (ABRT)
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 systemd-udevd[19533]: p0v53: Worker 
[1716040] failed
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 /usr/sbin/fpcStealConsole[19295]: 
/usr/sbin/event-daemonCoreDump.sh Wrote 
/var/crash/userfiles/core.systemd-udevd.1716040.6
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 /usr/sbin/fpcStealConsole[19295]: 
/usr/sbin/event-daemonCoreDump.sh: Sent log 2A5A0092: Process 
systemd-udevd.1716040 core dumped (6).
Mar  3 06:53:19 tok1-qz1-sr5-rk361-s04 kernel: I4 IDP2 578b7bb 0024/361-s04 
IN=vlan1.53 OUT= MAC=02:cc:ef:80:d1:11:52:70:89:51:de:08:08:00:45:00:00:45 
SRC=192.168.81.0 DST=192.168.105.8 LEN=69 TOS=0x00 PREC=0x00 TTL=63 ID=60189 DF 
PROTO=UDP SPT=53 DPT=62817 LEN=49


It is also interesting to see some mlx cmd request is being issues by kernel 
being shown as cmd failure much before the interface renaming calls ..We don't 
know whether this has any impact..but mentioning it here 
Mar 03 06:37:17.882760 tok1-qz1-sr5-rk361-s04 kernel: net_ratelimit: 280 
callbacks suppressed
Mar 03 06:37:17.882808 tok1-qz1-sr5-rk361-s04 kernel: IPv4: martian source 
192.168

[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server

2022-05-24 Thread Mario Limonciello

@KH:

Thanks for sharing that!  I agree with you.  I've sent this up to explicitly 
document the new behavior.
https://lore.kernel.org/linux-ide/20220524170508.563-4-mario.limoncie...@amd.com/T/#u

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

Title:
  SATA device hot plug regression on AMD EPYC (Asus) server

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux
  version 5.4.0-109-generic", but it works on earlier version of " Linux
  version 5.4.0-42-generic"

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


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

[Kernel-packages] [Bug 1973482] Re: kernel 4.15.0.177 break everything on Dell XPS 15 9570

2022-05-24 Thread Svenja

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

Same here on i5-8250U CPU with Linux Mint 19.1.
Unfortunately the same issue with linux-image-4.15.0-180-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/1973482

Title:
  kernel 4.15.0.177 break everything on Dell XPS 15 9570

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There are many issues including:

  - wireless card DISBLED / UNCLAIMED
  - no sound output device listed
  - strange electrical noise in the speakers when the cpu is under load
  - mounting /boot/efi hangs for 1m30
  - various services not starting (snap, etc)

  Rolling back to 4.15.0.176 fixes all the issues.

  Can you let me know which logs I could provide to help?

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18
  Uname: Linux 4.15.0-177-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 00:39:58 2022
  InstallationDate: Installed on 2018-12-15 (1247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   virbr0no wireless extensions.
   
   lono wireless extensions.
   
   virbr0-nic  no wireless extensions.
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic 
root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 
nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 
nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 
nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off 
mitigations=off clocksource=hpet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-177-generic N/A
   linux-backports-modules-4.15.0-177-generic  N/A
   linux-firmware  1.173.20
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1975509] Autopkgtest regression report (nvidia-graphics-drivers-510-server/510.73.08-0ubuntu0.21.10.1)

2022-05-24 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted nvidia-graphics-drivers-510-server 
(510.73.08-0ubuntu0.21.10.1) for impish have finished running.
The following regressions have been reported in tests triggered by the package:

pyopencl/2021.1.2-1build2 (armhf)


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/impish/update_excuses.html#nvidia-graphics-drivers-510-server

[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-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1975509

Title:
  Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal,
  Impish, Jammy, and Kinetic

Status in linux-restricted-modules package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510-server package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Impish:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Impish:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Jammy:
  Fix Committed
Status in linux-restricted-modules source package in Kinetic:
  Confirmed
Status in nvidia-graphics-drivers-510-server source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  === 510 kinetic/jammy/impish/focal/bionic ===

* New upstream release (LP: #1975509):
  - When calculating the address of grid barrier allocated for a CUDA 
stream, there was an off-by-one error. The address calculation is 
corrected in thisrelease.
  - An issue that caused an AC cycle test to fail with "AssertionError: 
NVLink links with inappropriate status found" is resolved.
  - An issue that caused NX 11 to become nonresponsive during a graphics 
operation is resolved.
  - Linking issues were observed when using libnvfm.so. Now and other 
depend tools use dynamic linking with libstdc++ and libgcc.
  - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some
non-fatal nvlink interrupts is resolved.

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


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

[Kernel-packages] [Bug 1970127] Re: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U)

2022-05-24 Thread Stefan

HP ENVY x360 with Ryzen 3700U 15-ds0xxx (2019):

Ubuntu 18.04, 20.04 works without issues.

Ubuntu 22.04 never gets past animated boot logo screen, stays there,
turning, waiting indefinitely. I'm booting in Legacy mode.

Notes: My network boot is disabled in UEFI, so that does not help. Safe
graphics do not help either.

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

Title:
  Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7
  3700U)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu-22.04-desktop-amd64.iso live cd does not boot on a HP ENVY
  X360 notebook (Ryzen 7 3700U).

  Model:
  HP ENVY X360
  13-ar0777ng
  9YN58EA#ABD

  After a few minutes the screen simply switches to black. No
  possibility to get a console by pressing CTRL-ALT-F1, F2, ...

  I removed the boot options "quiet splash" and recorded the boot via video.
  (just ask if you need the full video)
  I attach a significantly looking screenshot from that video, showing a kernel 
bug message.

  
  Currently the notebook runs with Ubuntu-20.04 using the Linux-5.11 HWE kernel.
  But suspend to memory isn't working.
  Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292

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


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

[Kernel-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

2022-05-24 Thread VAN LAETHEM

update installed and 
~$ NetworkManager -V
1.36.6

To test i need to be at another location. Feedback Thursday
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/1970799

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  With 20.04 I used a wifi connection with a hotspot Telenet with following 
parametres:
  security : WPA2 entreprise
  authentification : tunneled TLS
  no AC certificat drequired
  inner authentication : MSCHAPV2(non EAP)
  user name: my id
  password : my pswd

  with 22.04 it doesn’t work anymore nor with the internal broadcom wifi
  nor with dongles (nor my Dlink 140 nor TP-link WN7200)

  This problem is only present with hotspot requesting an identification
  (user+pswd) awith hotspots without identification everything is OK

  in appendice some infos
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michelvlt   1725 F pulseaudio
   /dev/snd/pcmC0D0p:   michelvlt   1725 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2022-04-21 (7 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IpRoute:
   default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 
   10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 
   169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 
   192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 
600
  MachineType: Apple Inc. MacBookPro8,1
  NonfreeKernelModules: wl
  Package: wpa
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 87.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245B3640C91C81
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245B3640C91C81
  dmi.modalias: 
dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro8,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+subscriptions


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

[Kernel-packages] [Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen

2022-05-24 Thread Andy Townsend

> I just installed kernel 4.15.0-180 ... problem is still there

Also for me - no problem in -176, but problems in -177 and -180.

If there's logs that it'd be useful to see, just ask.

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

Title:
  linux-image-4.15.0-177-generic freezes on the welcome screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.15.0-177-generic, my machine
  completely freezes on the Ubuntu Welcome screen, i.e. right after
  switching to GUI mode. The mouse pointer is frozen, the keyboard does
  not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows
  no reaction.

  I cannot work with my machine at this point and have to hard reset it.

  Selecting advanced boot options in grub and selecting the previous
  linux kernel 4.15.0-176 makes it work again. So this bad bug was
  introduced with the 4.15.0-177 kernel release.

  I tried removing the nvidia-driver-510 package, presumably making
  Ubuntu use the "nouveau" driver, and with that, I could use the
  welcome screen and log in, but the machine still froze shortly
  afterwards.

  So maybe this is some sort of interference with my GeForce 1080
  graphics card, but it is not specific to the driver used.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18
  Uname: Linux 4.15.0-176-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2082 F pulseaudio
   /dev/snd/controlC0:  robert 2082 F pulseaudio
   /dev/snd/controlC2:  robert 2082 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu May 12 13:36:28 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-29 (2386 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Supermicro Super Server
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic 
root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-176-generic N/A
   linux-backports-modules-4.15.0-176-generic  N/A
   linux-firmware  1.173.21
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago)
  dmi.bios.date: 09/18/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X11SAE
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Super Server
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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


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

[Kernel-packages] [Bug 1969482] Re: zfs-2.1.4+ sru

2022-05-24 Thread Brian Murray

I'm setting this back to verification-needed as we still need to hear
back from the kernel team about this part of the test plan:

 * kernel regression zfs testsuite pass

 * zsys integration test pass

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

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

Title:
  zfs-2.1.4+ sru

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * Upstream stable point release update with bugfixes, performance
  fixes, and newer kernel support as needed already in the OEM kernel
  and will be needed in the future HWE kernels.

  [Test Plan]

   * autopkgtest pass

   * kernel regression zfs testsuite pass

   * zsys integration test pass

  [Where problems could occur]

   * The stable branches maintain api/abi. Certain bugfixes do change
  userspace visible behavior of either succeeeding (when previously
  operations failed), or return errors when previously succeeding in
  error. For example there are changes when unlinking files in full
  volumes; changes to fallocate behaviour, etc. Overall they are minor
  corner cases, and bugfixes to correct the bahaviour to what is
  universally expected and how things behave on other filesystems (i.e.
  ext4).

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


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

[Kernel-packages] [Bug 1975635] [NEW] PC Freeze on 5.13.0.40

2022-05-24 Thread f1vjt

Public bug reported:

My pc freeze frequently with the last kernel, three times in two hours.
Recently when I use Firefox and/or pdf viewer (on Firefox or with Xreader).


System:Kernel: 5.13.0-37-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7 
   wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal 
Machine:   Type: Laptop System: LENOVO product: 80G0 v: Lenovo G50-30 serial: 
 Chassis: 
   type: 10 v: Lenovo G50-30 serial:  
   Mobo: LENOVO model: Lancer 5A6 v: 31900058WIN serial:  UEFI: 
LENOVO v: A7CN48WW 
   date: 08/03/2015 
Battery:   ID-1: BAT0 charge: 26.4 Wh condition: 26.4/28.5 Wh (93%) volts: 
16.3/14.4 model: Lenovo 
   serial:  status: Full 
CPU:   Topology: Quad Core model: Intel Pentium N3540 bits: 64 type: MCP 
arch: Silvermont 
   rev: 8 L2 cache: 1024 KiB 
   flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 
17333 
   Speed: 897 MHz min/max: 500/2666 MHz Core speeds (MHz): 1: 584 2: 
1010 3: 930 4: 838 
Graphics:  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & 
Display vendor: Lenovo 
   driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0f31 
   Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: 
fbdev,vesa 
   resolution: 1366x768~60Hz 
   OpenGL: renderer: Mesa DRI Intel HD Graphics (BYT) v: 4.2 Mesa 
21.2.6 compat-v: 3.0 
   direct render: Yes 
Audio: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High Definition 
Audio 
   vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip 
ID: 8086:0f04 
   Sound Server: ALSA v: k5.13.0-37-generic 
Network:   Device-1: Intel Wireless 3160 driver: iwlwifi v: kernel port: 2000 
bus ID: 02:00.0 
   chip ID: 8086:08b4 
   IF: wlp2s0 state: up mac:  
   Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Lenovo 
   driver: r8169 v: kernel port: 1000 bus ID: 03:00.0 chip ID: 
10ec:8168 
   IF: enp3s0 state: down mac:  
Drives:Local Storage: total: 245.88 GiB used: 30.06 GiB (12.2%) 
   ID-1: /dev/mmcblk0 type: USB model: SA08G size: 7.40 GiB serial: 
 
   ID-2: /dev/sda vendor: Micron model: 1100 SATA 256GB size: 238.47 
GiB speed: 3.0 Gb/s 
   serial:  
Partition: ID-1: / size: 233.24 GiB used: 26.60 GiB (11.4%) fs: ext4 dev: 
/dev/sda2 
Sensors:   System Temperatures: cpu: 50.0 C mobo: N/A 
   Fan Speeds (RPM): N/A 
Repos: No active apt repos in: /etc/apt/sources.list 
   Active apt repos in: 
/etc/apt/sources.list.d/dansmith-chirp-snapshots-focal.list 
   1: deb http: //ppa.launchpad.net/dansmith/chirp-snapshots/ubuntu 
focal main
   Active apt repos in: 
/etc/apt/sources.list.d/nrbrtx-python2-stuff-focal.list 
   1: deb http: //ppa.launchpad.net/nrbrtx/python2-stuff/ubuntu focal 
main
   Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
   1: deb http: //mirror6.layerjet.com/linuxmint/packages una main 
upstream import backport
   2: deb http: //ftp.rezopole.net/ubuntu focal main restricted 
universe multiverse
   3: deb http: //ftp.rezopole.net/ubuntu focal-updates main restricted 
universe multiverse
   4: deb http: //ftp.rezopole.net/ubuntu focal-backports main 
restricted universe multiverse
   5: deb http: //security.ubuntu.com/ubuntu/ focal-security main 
restricted universe multiverse
   6: deb http: //archive.canonical.com/ubuntu/ focal partner
Info:  Processes: 248 Uptime: 3m Memory: 7.65 GiB used: 1.61 GiB (21.0%) 
Init: systemd v: 245 
   runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Client: Unknown python3.8 
client inxi: 3.0.38

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

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

Title:
  PC Freeze on 5.13.0.40

Status in linux package in Ubuntu:
  New

Bug description:
  My pc freeze frequently with the last kernel, three times in two hours.
  Recently when I use Firefox and/or pdf viewer (on Firefox or with Xreader).

  
  System:Kernel: 5.13.0-37-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7 
 wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal 
  Machine:   Type: Laptop System: LENOVO product: 80G0 v: Lenovo G50-30 serial: 
 Chassis: 
 type: 10 v: Lenovo G50-30 serial:  
 Mobo: LENOVO model: Lancer 5A6 v: 31900058WIN serial:  
UEFI: LENOVO v: A7CN48WW 
 date: 08/03/2015 
  Battery:   ID-1: BAT0 charge: 26.4 Wh condition: 26.4/28.5 Wh (93%) volts: 
16.3/14.4 model: Lenovo 
 serial:  status: Full 
  CPU:   Topology: Quad Core model: Intel Pentium N3540 bits: 64 type: MCP 
arch: Si

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

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

apport-collect 1975635

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

Title:
  PC Freeze on 5.13.0.40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My pc freeze frequently with the last kernel, three times in two hours.
  Recently when I use Firefox and/or pdf viewer (on Firefox or with Xreader).

  
  System:Kernel: 5.13.0-37-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7 
 wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal 
  Machine:   Type: Laptop System: LENOVO product: 80G0 v: Lenovo G50-30 serial: 
 Chassis: 
 type: 10 v: Lenovo G50-30 serial:  
 Mobo: LENOVO model: Lancer 5A6 v: 31900058WIN serial:  
UEFI: LENOVO v: A7CN48WW 
 date: 08/03/2015 
  Battery:   ID-1: BAT0 charge: 26.4 Wh condition: 26.4/28.5 Wh (93%) volts: 
16.3/14.4 model: Lenovo 
 serial:  status: Full 
  CPU:   Topology: Quad Core model: Intel Pentium N3540 bits: 64 type: MCP 
arch: Silvermont 
 rev: 8 L2 cache: 1024 KiB 
 flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 
17333 
 Speed: 897 MHz min/max: 500/2666 MHz Core speeds (MHz): 1: 584 2: 
1010 3: 930 4: 838 
  Graphics:  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & 
Display vendor: Lenovo 
 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0f31 
 Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: 
fbdev,vesa 
 resolution: 1366x768~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics (BYT) v: 4.2 Mesa 
21.2.6 compat-v: 3.0 
 direct render: Yes 
  Audio: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High 
Definition Audio 
 vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
chip ID: 8086:0f04 
 Sound Server: ALSA v: k5.13.0-37-generic 
  Network:   Device-1: Intel Wireless 3160 driver: iwlwifi v: kernel port: 2000 
bus ID: 02:00.0 
 chip ID: 8086:08b4 
 IF: wlp2s0 state: up mac:  
 Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Lenovo 
 driver: r8169 v: kernel port: 1000 bus ID: 03:00.0 chip ID: 
10ec:8168 
 IF: enp3s0 state: down mac:  
  Drives:Local Storage: total: 245.88 GiB used: 30.06 GiB (12.2%) 
 ID-1: /dev/mmcblk0 type: USB model: SA08G size: 7.40 GiB serial: 
 
 ID-2: /dev/sda vendor: Micron model: 1100 SATA 256GB size: 238.47 
GiB speed: 3.0 Gb/s 
 serial:  
  Partition: ID-1: / size: 233.24 GiB used: 26.60 GiB (11.4%) fs: ext4 dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 50.0 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Repos: No active apt repos in: /etc/apt/sources.list 
 Active apt repos in: 
/etc/apt/sources.list.d/dansmith-chirp-snapshots-focal.list 
 1: deb http: //ppa.launchpad.net/dansmith/chirp-snapshots/ubuntu 
focal main
 Active apt repos in: 
/etc/apt/sources.list.d/nrbrtx-python2-stuff-focal.list 
 1: deb http: //ppa.launchpad.net/nrbrtx/python2-stuff/ubuntu focal 
main
 Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
 1: deb http: //mirror6.layerjet.com/linuxmint/packages una main 
upstream import backport
 2: deb http: //ftp.rezopole.net/ubuntu focal main restricted 
universe multiverse
 3: deb http: //ftp.rezopole.net/ubuntu focal-updates main 
restricted universe multiverse
 4: deb http: //ftp.rezopole.net/ubuntu focal-backports main 
restricted universe multiverse
 5: deb http: //security.ubuntu.com/ubuntu/ focal-security main 
restricted universe multiverse
 6: deb http: //archive.canonical.com/ubuntu/ focal partner
  Info:  Processes: 248 Uptime: 3m Memory: 7.65 GiB used: 1.61 GiB (21.0%) 
Init: systemd v: 245 
 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Client: Unknown python3.8 
client inxi: 3.0.38

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


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

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2022-05-24 Thread Guilherme G. Piccoli

Thanks Kellen and Cascardo.

Kellen, nice that you're willing to work on that - this is a long
standing problem and that work would be definitely appreciated by the
Ubuntu community, be it free users or the Ubuntu Advantage customers!

Cascardo, about your two risks:

(a) Partially agree with that. I agree with the part of testing,
definietly this is the big chunk of work here. But I disagree with the
retrocompatibility claim: of course we need to enforce that, but it's
not that difficult in the LTS->LTS+1 model. See, we have a small number
of HWE kernel per LTS release, I guess 4 or 5 correct? We need to be
sure the makedumpfile updates are compatible with them, and that's it.

If I'm talking Focal and some makedumpfile update (unintentionally) breaks
dumps for kernel 4.19 or prior, why should we care if that's an unsupported
scenario?
IMHO it's much better to ensure that every HWE kernel receives a proper
functional makedumpfile update, instead of an overly cautious attitude with
older/unsupported kernels.

(b) I agree here, but I guess the effort of SRU exception/ LTS->LTS+1
model will only make it easier. Imagine if when Ubuntu version X is
released the upstream makedumpfile is not handling well the recent
kernel version used by X - so we could either fix (or report) the
makedumpfile issue quickly (especially due to part (a) above, the
improved testing). Then, once it's fixed either by Canonical or
community, this could quickly be integrated through a fast process, a
version bump for makedumpfile for example.

In the end, I think testing is the key word here - the more serious and
thorough tests makedumpfile has, the more confidence in such model we'd
have. But hopefully with Kellen's effort this stops preventing a more
proactive approach with makedumpfile from happening, by updating it
before users report bugs (which has been happening since forever for
this package).

Cheers!

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

Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."

Status in makedumpfile package in Ubuntu:
New

Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."

* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.

* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:

https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900

[PATCH] Increase SECTION_MAP_LAST_BIT to 5

* Required for kernel 5.12

Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:

__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.

Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.

Signed-off-by: Kazuhito Hagio

[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.

* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.

* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.

[Where problems could occur]

* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.

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

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

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2022-05-24 Thread Thadeu Lima de Souza Cascardo

Hi, Guilherme.

I think you misunderstood and we are in agreement. What I mean by the
first point is that, on Focal, we need to support 5.4 and 5.15. I don't
even think we need to support 5.8 and 5.11 any longer, though 5.13, as
it will still be supported for a while needs supporting. But I also mean
that we should support not only 5.4.0-113 and 5.4.0-114 (versions on
-updates and -proposed), we should also support older 5.4 versions (one
could argue all the versions that are still livepatchable at least). I
don't think the risk of regressions is big here, but it exists. We ought
to balance that risk and how much we can test.

About the second point, it's just an argument that we should not
restrict ourselves to the upstream major makedumpfile version that is in
LTS+1. Take focal, which will receive 5.15 from jammy. It may require a
newer makedumpfile than the one in Jammy because the one in Jammy may
not be sufficient to support 5.15.

Cascardo.

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

Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."

Status in makedumpfile package in Ubuntu:
New

Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."

* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.

* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:

https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900

[PATCH] Increase SECTION_MAP_LAST_BIT to 5

* Required for kernel 5.12

Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.

Signed-off-by: Kazuhito Hagio

[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.

* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.

* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.

[Where problems could occur]

* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.

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

[Kernel-packages] [Bug 1971933] Re: [Regression] Unable to wake laptop using trackpad input

@kaihengfeng any workarounds?
The device node 
"/sys/devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00" 
doesn't have "wakeup" file to write "enabled" to ...

Am I missing something ?

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

Title:
  [Regression] Unable to wake laptop using trackpad input

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to Ubuntu 22.04,
  the dell laptop no longer wakes up using trackpad movement/interaction.

  Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e.,
  Working On:
  Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10.

  NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31
  )

  Just to clarify: Suspend and Resume are working, trackpad is functional 
before and after suspend,
  But,
  Trackpad trigger to wakeup from suspend is not working.

  --

  $ cat /proc/version_signature > version.log
  => Ubuntu 5.15.0-27.28-generic 5.15.30

  -

  $ lsb_release -rd
  =>
  Description:Ubuntu 22.04 LTS
  Release:22.04

  -

  $ apt-cache policy linux-image-generic
  =>
  linux-image-generic:
    Installed: 5.15.0.27.30
    Candidate: 5.15.0.27.30
    Version table:
   *** 5.15.0.27.30 500
  500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 
Packages
  500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages

  -

  What I expected to happen:
  Laptop wakes-up from suspend on touchpad interaction

  -

  What happened:
  Laptop did not wakeup from suspend on touchpad interaction.

  Laptop woke up on the press of power button.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.27.30
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  monkey 5198 F wireplumber
   /dev/snd/controlC1:  monkey 5198 F wireplumber
   /dev/snd/seq:monkey 5195 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri May  6 12:40:22 2022
  InstallationDate: Installed on 2018-10-25 (1288 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 
2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau 
nouveau.modeset=0 vt.handoff=7
  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-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1975649] [NEW] flowtable: fix TCP flow teardown

2022-05-24 Thread Bodong Wang

Public bug reported:

* Explain the feature

This patch addresses three possible problems:

1. ct gc may race to undo the timeout adjustment of the packet path, leaving
   the conntrack entry in place with the internal offload timeout (one day).

2. ct gc removes the ct because the IPS_OFFLOAD_BIT is not set and the CLOSE
   timeout is reached before the flow offload del.

3. tcp ct is always set to ESTABLISHED with a very long timeout
   in flow offload teardown/delete even though the state might be already
   CLOSED. Also as a remark we cannot assume that the FIN or RST packet
   is hitting flow table teardown as the packet might get bumped to the
   slow path in nftables.

This patch resets IPS_OFFLOAD_BIT from flow_offload_teardown(), so
conntrack handles the tcp rst/fin packet which triggers the CLOSE/FIN
state transition.

Moreover, return the connection's ownership to conntrack upon teardown
by clearing the offload flag and fixing the established timeout value.
The flow table GC thread will asynchonrnously free the flow table and
hardware offload entries.

Before this patch, the IPS_OFFLOAD_BIT remained set for expired flows on
which is also misleading since the flow is back to classic conntrack
path.

If nf_ct_delete() removes the entry from the conntrack table, then it
calls nf_ct_put() which decrements the refcnt. This is not a problem
because the flowtable holds a reference to the conntrack object from
flow_offload_alloc() path which is released via flow_offload_free().

This patch also updates nft_flow_offload to skip packets in SYN_RECV
state. Since we might miss or bump packets to slow path, we do not know
what will happen there while we are still in SYN_RECV, this patch
postpones offload up to the next packet which also aligns to the
existing behaviour in tc-ct.

flow_offload_teardown() does not reset the existing tcp state from
flow_offload_fixup_tcp() to ESTABLISHED anymore, packets bump to slow
path might have already update the state to CLOSE/FIN.

* How to test
Adding the following flows to the OVS bridge in DPU OS:
# ovs-ofctl add-flow ovsbr1 "table=0, ip,ct_state=-trk, actions=ct(table=1)"
# ovs-ofctl add-flow ovsbr1 "table=1, ip,ct_state=+new, 
actions=ct(commit),normal"
# ovs-ofctl add-flow ovsbr1 "table=1, ip,ct_state=-new, actions=normal"

Start netserver on SUT:
# netserver -p 5007

Start multiple TCP_CRR tests on peer:
# count=1;while [ $count -lt 10 ]; do screen -d -m netperf -t TCP_CRR -H 
11.0.0.2 -l 360  -- -r 1 -O " MIN_LAETENCY, MAX_LATENCY, MEAN_LATENCY, 
P90_LATENCY, P99_LATENCY ,P999_LATENCY,P_LATENCY,STDDEV_LATENCY ,THROUGHPUT 
,THROUGHPUT_UNITS "; count=`expr $count + 1`; done
A huge number of connections will be established and tear down. After the 
tests, some of them are not aged out:
# From /proc/net/nf_conntrack in DPU OS
ipv4 2 tcp  6 86354 LAST_ACK src=11.0.0.1 dst=11.0.0.2 sport=35862 
dport=46797 src=11.0.0.2 dst=11.0.0.1 sport=46797 dport=35862 [ASSURED] mark=0 
zone=0 use=2
ipv4 2 tcp  6 86354 LAST_ACK src=11.0.0.1 dst=11.0.0.2 sport=35862 
dport=46797 src=11.0.0.2 dst=11.0.0.1 sport=46797 dport=35862 [ASSURED] mark=0 
zone=0 use=2
ipv4 2 tcp  6 86354 LAST_ACK src=11.0.0.1 dst=11.0.0.2 sport=35862 
dport=46797 src=11.0.0.2 dst=11.0.0.1 sport=46797 dport=35862 [ASSURED] mark=0 
zone=0 use=2
The issue is usually reproduced after running the for several times.

* What it could break.
N/A

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

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

Title:
  flowtable: fix TCP flow teardown

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  * Explain the feature

  This patch addresses three possible problems:

  1. ct gc may race to undo the timeout adjustment of the packet path, leaving
 the conntrack entry in place with the internal offload timeout (one day).

  2. ct gc removes the ct because the IPS_OFFLOAD_BIT is not set and the CLOSE
 timeout is reached before the flow offload del.

  3. tcp ct is always set to ESTABLISHED with a very long timeout
 in flow offload teardown/delete even though the state might be already
 CLOSED. Also as a remark we cannot assume that the FIN or RST packet
 is hitting flow table teardown as the packet might get bumped to the
 slow path in nftables.

  This patch resets IPS_OFFLOAD_BIT from flow_offload_teardown(), so
  conntrack handles the tcp rst/fin packet which triggers the CLOSE/FIN
  state transition.

  Moreover, return the connection's ownership to conntrack upon teardown
  by clearing the offload flag and fixing the established timeout value.
  The flow table GC thread will asynchonrnously free the flow table and
  hardware offload entries.

  Before this patch, the IPS_OFFLOAD_BIT remained set for expired flows on
  which is also misleading since

[Kernel-packages] [Bug 1970411] Re: gnome-remote-desktop-daemon crashes on fuse_thread_func → g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per missing fusermount3)

2022-05-24 Thread Brian Murray

Hello errors.ubuntu.com, or anyone else affected,

Accepted gnome-remote-desktop into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-remote-
desktop/42.1.1-0ubuntu1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-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/1970411

Title:
  gnome-remote-desktop-daemon crashes on fuse_thread_func →
  g_thread_proxy → start_thread: Failed to mount FUSE filesystem (as per
  missing fusermount3)

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in gnome-remote-desktop source package in Jammy:
  Fix Committed
Status in gnome-remote-desktop package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  GNOME Remote desktop crashes if fuse3 package is not installed as it provides 
fusermount3, that fuse_session_mount() implicitly requires.

  Test Case
  =
  Verify that gnome-remote-desktop has a dependency on fuse3

  What Could Go Wrong
  ==
  This just adds a dependency.

  This bug should be very uncommon because a system without fuse3 also
  wouldn't have xdg-desktop-portal installed meaning Snaps don't work
  and wouldn't have ubuntu-desktop-minimal installed.

  Other Info
  =
  libfuse3 is currently suggesting fusermount3, I'm wondering if we should 
instead recommending it, given that one of the library function relies on that. 
It's possible for things to use the library without that function so that's why 
it's proposed to be only a Recommends and not a Depends.

  For Ubuntu 22.10, we should see if the kernel can support this
  natively without needing fusermount3 as suggested in comment 1.

  
  Stack trace:

  #0  g_log_structured_array (log_level=, fields=0x7f7859fefdd0, 
n_fields=3) at ../../../glib/gmessages.c:557
  writer_func = 
  writer_user_data = 
  recursion = 
  depth = 
  __func__ = "g_log_structured_array"
  _g_boolean_var_ = 
  #1  0x7f79092e2f99 in g_log_default_handler 
(log_domain=log_domain@entry=0x0, log_level=log_level@entry=6, 
message=message@entry=0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem", unused_data=unused_data@entry=0x0) at 
../../../glib/gmessages.c:3295
  fields = {{key = 0x7f790933cb12 "GLIB_OLD_LOG_API", value = 
0x7f790933a611, length = -1}, {key = 0x7f790933ca4d "MESSAGE", value = 
0x7f786f80, length = -1}, {key = 0x7f790933ca60 "PRIORITY", value = 
0x7f790939a109, length = -1}, {key = 0x7f790932a09f  
"\205\300t\025H\215\065\326\377\006", value = 0x7f7859ff3640, length = 
140157821898257}}
  n_fields = 
  #2  0x7f79092e43fa in g_logv (log_domain=0x0, 
log_level=G_LOG_LEVEL_ERROR, format=, args=) at 
../../../glib/gmessages.c:1387
  domain = 0x0
  data = 0x0
  depth = 
  log_func = 0x7f79092e2ee0 
  domain_fatal_mask = 
  masquerade_fatal = 0
  test_level = 6
  was_fatal = 
  was_recursion = 
  buffer = 
  msg = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  msg_alloc = 0x7f786f80 "[FUSE Clipboard] Failed to mount FUSE 
filesystem"
  i = 2
  size = 
  #3  0x7f79092e46e3 in g_log (log_domain=log_domain@entry=0x0, 
log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x5605ec5e3c38 
"[FUSE Clipboard] Failed to mount FUSE filesystem") at 
../../../glib/gmessages.c:1456
  args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 
0x7f7859ff, reg_save_area = 0x7f7859feff40}}
  #4  0x5605ec5c0920 in fuse_thread_func (data=0x5605ed30182

[Kernel-packages] [Bug 1975516] Re: System freeze

2022-05-24 Thread Douglas Silva

It happened again, with the laptop idle same as before.

This time the screen went dark (backlight off) and the fans were
spinning fast. I could feel the laptop was a bit hot.

I had Transmission, LibreOffice Writer and GNOME Files running at the
time.

** Attachment added: "journalctl log of the second freeze"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+attachment/5592731/+files/journalctl_2.log

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

Title:
  System freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I had LibreOffice Writer open at the time, but it was idle. The system
  became completely unresponsive and a power reset was the only way to
  shut it down. The "REISUB" command didn't work.

  I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible
  with them.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 1511 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 23 13:48:05 2022
  InstallationDate: Installed on 2022-05-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3583
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic 
root=UUID=15cac922-78d2-4c88-aa40-a49c2bfda033 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-33-generic N/A
   linux-backports-modules-5.15.0-33-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2021
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0DC2CG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd04/21/2021:br1.13:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3583
  dmi.product.sku: 08CA
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."

2022-05-24 Thread dann frazier

Thanks everyone for trying to tackle this long-standing issue. fwiw,
here's my $0.02 no how we could proceed:

Someone should draft a special case page for makedumpfile:
https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases
I'm happy to review/provide feedback, but I'd rather someone who would be
carrying out the plan drive it.

As others have mentioned, testing is the hard part, and we need to
define what will be tested in the special case documentation. Since
makedumpfile is really just a filter, I don't think we need to (or
reasonably could) boot a bunch of systems in different configs and
generate crashdumps for every new update. Rather, i think we could build
a repository of representative, unfiltered, /proc/vmcore files that
focal's existing makedumpfile can parse. Then we can just check that all
of those files can still be parsed by the proposed makedumpfile. With
some scripting and a multi-architecture cloud, this could be automated.
In fact, if this vmcore repo were online, we could implement this an
autopkgtest (w/ needs-internet set). But we should also do at least one
end-to-end kdump, just to make sure the kdump-tools->makedumpfile
interface hasn't been broken.

What is a representative sample? One of each of the current LTS and HWE
kernels on amd64, arm64, ppc64el and s390x seems like an obvious start
(or the subset of those that actually work today). I don't think the
machine type is as important, VMs should be fine IMO. If we know of
examples where different machines expose structures differently in a way
that makedumpfile cares about, then perhaps add those as well. Once a
new makedumpfile lands that adds support for a new HWE kernel, we should
probably then update the repo w/ vmcore samples from that kernel, so we
can make sure the next update doesn't regress that support (probably
convenient to do when verifying the SRU, since I imagine we'd be testing
that it works w/ the new HWE kernel then anyway).

It'd be good to note in the special case request that kdump-tools does fall
back to a raw /proc/vmcore file cp if makedumpfile fails, which can mitigate
regressions for a subset of users
- those with the necessary disk space and lack of time constraints.

While I agree that crash falls into the same category, I don't think it
necessarily needs to happen at the same time. Obviously users running
focal need to dump their vmcore using focal - bug for developers
debugging a crash, I don't think it is to onerous to use a newer version
of Ubuntu. Again, I'm no saying we *shouldn't* add crash to the special
case, it just seems like a makedumpfile exception is significantly more
important.

Finally, I don't think we need to commit to a frequency of backports, or
a point at which they will stop. Rather we can just stick to agreeing on
how it *can* be done when someone has the time/interest in doing it.
Guillherme's LTS->LTS+1 scheme sounds like a reasonable pattern to shoot
for, but if that doesn't happen every time, we're still improving the
situation over the status quo.

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

Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."

Status in makedumpfile package in Ubuntu:
New

Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."

* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.

* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:

https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6

commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900

[PATCH] Increase SECTION_MAP_LAST_BIT to 5

* Required for kernel 5.12

Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.

Signed-off-by: Kazuhito Hagio

[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.

* Confirm that the patched makedu

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-5.4/5.4.0.1073.55)

2022-05-24 Thread Ubuntu SRU Bot

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

lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1971576] Re: SATA device hot plug regression on AMD EPYC (Asus) server

2022-05-24 Thread Zhanglei Mao

@Mario, May I ask you another 2 extending questions. 
   
  A. What is results in a AMD client( like laptop)? I thought this hot plug 
works out of box in client, what cause this difference from kernel/code?  

  B. I was told that hot plug works out of box on their Intel's server.
What cause this difference?

thanks,
Mao

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

Title:
  SATA device hot plug regression on AMD EPYC (Asus) server

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SATA disk hot plug can't work on Ubuntu 20.04 ga-kernel of "Linux
  version 5.4.0-109-generic", but it works on earlier version of " Linux
  version 5.4.0-42-generic"

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


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

[Kernel-packages] [Bug 1971164] Re: [Azure][CVM] hv/bounce buffer: Fix a race that can fail disk detection

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

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

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


** Tags added: verification-needed-focal

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

Title:
  [Azure][CVM] hv/bounce buffer: Fix a race that can fail disk detection

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

Bug description:
  SRU Justification

  [Impact]

  The linux-azure-cvm kernel (e.g. Ubuntu-azure-cvm-5.4.0-1078.81+cvm1)
  has a race condition bug in the Linux vmbus bounce buffer code
  (drivers/hv/hv_bounce.c), and as a result somtimes the kenrel fails to
  detect some of the SCSI disks, and the Linux dmesg log may show one of
  the 2 messages:

  #1: [ 2.995732] sd 3:0:0:3: [sdd] Sector size 0 reported, assuming
  512.

  #2: [ 3.651293] scsi host3: scsi scan: INQUIRY result too short (5),
  using 36

  Sometimes I see a strange call-trace (the 'order's is 18, if I print it)
  2022-04-26T20:10:18,398144+00:00 kmalloc_order_trace+0x1e/0x80
  2022-04-26T20:10:18,398147+00:00 __kmalloc+0x3ae/0x4c0
  2022-04-26T20:10:18,398150+00:00 __scsi_scan_target+0x283/0x590
  2022-04-26T20:10:18,398155+00:00 scsi_scan_channel.part.16+0x62/0x80
  2022-04-26T20:10:18,398158+00:00 scsi_scan_host_selected+0xd5/0x150
  2022-04-26T20:10:18,398160+00:00 store_scan+0xc8/0xe0
  (This is very strange because 'order 18' means (1 << 18) * 4096 bytes = 
1GBytes.)

  After some investigation, we eventually got the root cause and made a fix:
  
https://github.com/dcui/linux-azure-cvm/commit/ddde4dc33242794000e1d9667a5f9cfa31c15fdf

  With the fix, we no longer see the above strange symptoms.
  Please include the fix into the next release of the v5.4 linux-azure-cvm 
kernel. Thanks!

  [Test case]

  Microsoft tested

  [Where things could go wrong]

  Some SCSI drives may continue to go undetected.

  [Other Info]

  SF: #00335631

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


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

[Kernel-packages] [Bug 1972802] Re: enable config for fixing 5.17 kernel won't load mok

2022-05-24 Thread Yuan-Chen Cheng

5.17-oem-1007 kernel have the fix, wait it's landing and then do
verification.

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

Title:
  enable config for fixing 5.17 kernel won't load mok

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Mok keys is not trusted after kernel 5.17

  [Fix]
  Enable the CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT and CONFIG_IMA_ARCH_POLICY 
for fixing the patch
  "[patch] integrity: Do not load MOK and MOKx when secure boot be disabled" 
was added to check if secureboot enabled for trusting the MOK key

  [Test]
  Enroll Mok key and use it to sign kernel modules, make sure secure boot is on 
and load the kernel module by either modprobe or insmod.

  [Where problems could occur]
  Low. only affect the checking secureboot enable function.

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


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

[Kernel-packages] [Bug 1975621] [NEW] [Star Labs Lite IV] screen flashes on-off unless PSR is turned off

You have been subscribed to a public bug:

Laptop is a Starlabs Lite Mv IV
Integrated graphic card is Mesa Intel® UHD Graphics 605 (GLK 3)

Screen backlight turns off and on quickly from time to time
Seems to be random : can happen several times per minute, then nothing happens 
for a few minutes. Seems to happen more often if the graphic card load is 
increased. Might be related to the graphic card core temperature/load-related.

Fixed the problem by adding the following kernel option :
i915.enable_psr=0

[3.868968] i915 :00:02.0: [drm] Unknown revid 0x06
[3.869555] i915 :00:02.0: [drm] VT-d active for gfx access
[3.869566] fb0: switching to i915 from EFI VGA
[3.869878] i915 :00:02.0: vgaarb: deactivate vga console
[3.921387] i915 :00:02.0: [drm] couldn't get memory information
[3.922325] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[3.923660] i915 :00:02.0: [drm] Finished loading DMC firmware 
i915/glk_dmc_ver1_04.bin (v1.4)
[4.222037] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0
[4.222440] snd_hda_intel :00:0e.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[4.561945] fbcon: i915drmfb (fb0) is primary device
[4.593816] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device
[ 4954.090871] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun


Machine has latest firmware (CoreBoot)
And its Ubuntu is the latest LTS, kept up to date.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue May 24 19:38:39 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 06) (prog-if 
00 [VGA controller])
   Subsystem: Intel Corporation GeminiLake [UHD Graphics 605] [8086:2212]
InstallationDate: Installed on 2022-04-26 (28 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Star Labs Lite
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash mitigations=off 
i915.enable_psr=0 vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2022
dmi.bios.release: 4.16
dmi.bios.vendor: coreboot
dmi.bios.version: 4.16
dmi.board.name: Lite
dmi.board.vendor: Star Labs
dmi.board.version: 1.0
dmi.chassis.type: 9
dmi.chassis.vendor: Star Labs
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 1.0
dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
dmi.product.family: I4
dmi.product.name: Lite
dmi.product.sku: I4
dmi.product.version: 1.0
dmi.sys.vendor: Star Labs
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
[Star Labs Lite IV] screen flashes on-off unless PSR is turned off
https://bugs.launchpad.net/bugs/1975621
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 1975621] Re: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off

2022-05-24 Thread Daniel van Vugt

** Summary changed:

- screen flashes on-off unless PSR is turned off 
+ [Star Labs Lite IV] screen flashes on-off unless PSR is turned off

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

** Tags added: psr

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

Title:
  [Star Labs Lite IV] screen flashes on-off unless PSR is turned off

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop is a Starlabs Lite Mv IV
  Integrated graphic card is Mesa Intel® UHD Graphics 605 (GLK 3)

  Screen backlight turns off and on quickly from time to time
  Seems to be random : can happen several times per minute, then nothing 
happens for a few minutes. Seems to happen more often if the graphic card load 
is increased. Might be related to the graphic card core 
temperature/load-related.

  Fixed the problem by adding the following kernel option :
  i915.enable_psr=0

  [3.868968] i915 :00:02.0: [drm] Unknown revid 0x06
  [3.869555] i915 :00:02.0: [drm] VT-d active for gfx access
  [3.869566] fb0: switching to i915 from EFI VGA
  [3.869878] i915 :00:02.0: vgaarb: deactivate vga console
  [3.921387] i915 :00:02.0: [drm] couldn't get memory information
  [3.922325] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [3.923660] i915 :00:02.0: [drm] Finished loading DMC firmware 
i915/glk_dmc_ver1_04.bin (v1.4)
  [4.222037] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on 
minor 0
  [4.222440] snd_hda_intel :00:0e.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.561945] fbcon: i915drmfb (fb0) is primary device
  [4.593816] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device
  [ 4954.090871] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  
  Machine has latest firmware (CoreBoot)
  And its Ubuntu is the latest LTS, kept up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 24 19:38:39 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 06) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation GeminiLake [UHD Graphics 605] [8086:2212]
  InstallationDate: Installed on 2022-04-26 (28 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash mitigations=off 
i915.enable_psr=0 vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)

2022-05-24 Thread Daniel van Vugt

Pipewire isn't involved in putting pixels on the screen.

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

Title:
  [nouveau] Weird colors after startup (Ubuntu 22.04)

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [Workaround/Fix]

  1. When starting the Ubuntu live image, select the option 'Ubuntu
  (safe graphics)' from the boot menu.

  2. During installation be sure to select the third-party software
  option checkbox in order to get the right Nvidia driver installed.

  [Original Description]

  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7C56
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  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.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):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-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

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

This change was made by a bot.

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

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

Title:
  [Star Labs Lite IV] screen flashes on-off unless PSR is turned off

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Starlabs Lite Mv IV
  Integrated graphic card is Mesa Intel® UHD Graphics 605 (GLK 3)

  Screen backlight turns off and on quickly from time to time
  Seems to be random : can happen several times per minute, then nothing 
happens for a few minutes. Seems to happen more often if the graphic card load 
is increased. Might be related to the graphic card core 
temperature/load-related.

  Fixed the problem by adding the following kernel option :
  i915.enable_psr=0

  [3.868968] i915 :00:02.0: [drm] Unknown revid 0x06
  [3.869555] i915 :00:02.0: [drm] VT-d active for gfx access
  [3.869566] fb0: switching to i915 from EFI VGA
  [3.869878] i915 :00:02.0: vgaarb: deactivate vga console
  [3.921387] i915 :00:02.0: [drm] couldn't get memory information
  [3.922325] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [3.923660] i915 :00:02.0: [drm] Finished loading DMC firmware 
i915/glk_dmc_ver1_04.bin (v1.4)
  [4.222037] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on 
minor 0
  [4.222440] snd_hda_intel :00:0e.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.561945] fbcon: i915drmfb (fb0) is primary device
  [4.593816] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device
  [ 4954.090871] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  
  Machine has latest firmware (CoreBoot)
  And its Ubuntu is the latest LTS, kept up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 24 19:38:39 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 06) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation GeminiLake [UHD Graphics 605] [8086:2212]
  InstallationDate: Installed on 2022-04-26 (28 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 003: ID 0c45:6365 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Star Labs Lite
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic 
root=UUID=740b6435-2b07-4154-8c4f-a1caaab7021a ro quiet splash mitigations=off 
i915.enable_psr=0 vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2022
  dmi.bios.release: 4.16
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.16
  dmi.board.name: Lite
  dmi.board.vendor: Star Labs
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Star Labs
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.16:bd05/11/2022:br4.16:efr1.0:svnStarLabs:pnLite:pvr1.0:rvnStarLabs:rnLite:rvr1.0:cvnStarLabs:ct9:cvr1.0:skuI4:
  dmi.product.family: I4
  dmi.product.name: Lite
  dmi.product.sku: I4
  dmi.product.version: 1.0
  dmi.sys.vendor: Star Labs
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Kernel-packages] [Bug 1975635] Re: PC Freeze on 5.13.0.40

2022-05-24 Thread Chris Guiver

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided
with Ubuntu by default, many require manual addition for some releases
of downstream OSes based on Ubuntu (eg. Linux Mint). You should check
with your distribution first.

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

Title:
  PC Freeze on 5.13.0.40

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My pc freeze frequently with the last kernel, three times in two hours.
  Recently when I use Firefox and/or pdf viewer (on Firefox or with Xreader).

  
  System:Kernel: 5.13.0-37-generic x86_64 bits: 64 compiler: N/A Desktop: 
Cinnamon 5.2.7 
 wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una base: Ubuntu 
20.04 focal 
  Machine:   Type: Laptop System: LENOVO product: 80G0 v: Lenovo G50-30 serial: 
 Chassis: 
 type: 10 v: Lenovo G50-30 serial:  
 Mobo: LENOVO model: Lancer 5A6 v: 31900058WIN serial:  
UEFI: LENOVO v: A7CN48WW 
 date: 08/03/2015 
  Battery:   ID-1: BAT0 charge: 26.4 Wh condition: 26.4/28.5 Wh (93%) volts: 
16.3/14.4 model: Lenovo 
 serial:  status: Full 
  CPU:   Topology: Quad Core model: Intel Pentium N3540 bits: 64 type: MCP 
arch: Silvermont 
 rev: 8 L2 cache: 1024 KiB 
 flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 
17333 
 Speed: 897 MHz min/max: 500/2666 MHz Core speeds (MHz): 1: 584 2: 
1010 3: 930 4: 838 
  Graphics:  Device-1: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & 
Display vendor: Lenovo 
 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0f31 
 Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: 
fbdev,vesa 
 resolution: 1366x768~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics (BYT) v: 4.2 Mesa 
21.2.6 compat-v: 3.0 
 direct render: Yes 
  Audio: Device-1: Intel Atom Processor Z36xxx/Z37xxx Series High 
Definition Audio 
 vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
chip ID: 8086:0f04 
 Sound Server: ALSA v: k5.13.0-37-generic 
  Network:   Device-1: Intel Wireless 3160 driver: iwlwifi v: kernel port: 2000 
bus ID: 02:00.0 
 chip ID: 8086:08b4 
 IF: wlp2s0 state: up mac:  
 Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Lenovo 
 driver: r8169 v: kernel port: 1000 bus ID: 03:00.0 chip ID: 
10ec:8168 
 IF: enp3s0 state: down mac:  
  Drives:Local Storage: total: 245.88 GiB used: 30.06 GiB (12.2%) 
 ID-1: /dev/mmcblk0 type: USB model: SA08G size: 7.40 GiB serial: 
 
 ID-2: /dev/sda vendor: Micron model: 1100 SATA 256GB size: 238.47 
GiB speed: 3.0 Gb/s 
 serial:  
  Partition: ID-1: / size: 233.24 GiB used: 26.60 GiB (11.4%) fs: ext4 dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 50.0 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Repos: No active apt repos in: /etc/apt/sources.list 
 Active apt repos in: 
/etc/apt/sources.list.d/dansmith-chirp-snapshots-focal.list 
 1: deb http: //ppa.launchpad.net/dansmith/chirp-snapshots/ubuntu 
focal main
 Active apt repos in: 
/etc/apt/sources.list.d/nrbrtx-python2-stuff-focal.list 
 1: deb http: //ppa.launchpad.net/nrbrtx/python2-stuff/ubuntu focal 
main
 Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
 1: deb http: //mirror6.layerjet.com/linuxmint/packages una main 
upstream import backport
 2: deb http: //ftp.rezopole.net/ubuntu focal main restricted 
universe multiverse
 3: deb http: //ftp.rezopole.net/ubuntu focal-updates main 
restricted universe multiverse
 4: deb http: //ftp.rezopole.net/ubuntu focal-backports main 
restricted universe multiverse
 5: deb http: //security.ubuntu.com/ubuntu/ focal-security main 
restricted universe multiverse
 6: deb http: //archive.canonical.com/ubuntu/ focal partner
  Info:  Processes: 248 Uptime: 3m Memory: 7.65 GiB used: 1.61 GiB (21.0%) 
Init: systemd v: 245 
 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Client: Unknown python3.8 
client inxi: 3.0.38

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


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

[Kernel-packages] [Bug 1972134] Re: AMD APU s2idle is broken after the ASIC reset fix

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

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

Title:
  AMD APU s2idle is broken after the ASIC reset fix

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The AMD based system can not reach s2idle after fix for LP: #1968475.

  [Fix]
  No need to evict resources for s2idle case.

  [Test]
  Test on a Cezanne, confirmed the 5.14.0-1035 breaks s2idle, and applying
  the fix can make s2idle work again.

  [Where problems could occur]
  The fix only applies to AMD APU, and the resources sould stay at carved
  out region over sleep.

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


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

[Kernel-packages] [Bug 1970927] Re: r8152 tx status -71