[Kernel-packages] [Bug 1982070] Re: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed
I can not reproduce on 5.4.0-125.141-generic kernel. The only Ubuntu kernel affected is 5.15. ** Changed in: kunpeng920/ubuntu-20.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982070 Title: scsi: hisi_sas: Increase debugfs_dump_index after dump is completed Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: [Impact] Trigger dump on hisi_sas in debugfs will cause kernel oops. [Test Plan] 1) modprobe hisi_sas_main with "debugfs_enable=1" 2) echo 1 | sudo tee /sys/kernel/debug/hisi_sas/\:74\:02.0/trigger_dump 3) dmesg | grep Oops [Regression Risk] Only touch code in hisi_sas. Need to run full test on hisi_sas. Other drivers/platforms are not affected. [Bug Description] When the hisi_sas_main driver is loaded, the DFX function is enabled. When the dump is triggered or the SAS controller is reset, call_trace is displayed. In addition, the hisi_sas_v3_hw driver is occupied and cannot be uninstalled. [Steps to Reproduce] 1)dmesg -C 2)dmesg 3)lsblk 4)lsscsi -p 5)lsmod | grep hisi_sas_v3 6)rmmod hisi_sas_v3_hw 7)rmmod hisi_sas_main 8)modprobe hisi_sas_main debugfs_enable=1 9)modprobe hisi_sas_v3_hw 10)cd /sys/kernel/debug/hisi_sas/\:74\:02.0/ 11)ll 12)echo 1 > trigger_dump 13)echo 1 > trigger_dump 14)dmesg [Actual Results] [ 1005.899976] sas: broadcast received: 0 [ 1005.87] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.901775] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.901777] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.901793] sas: broadcast received: 0 [ 1005.901820] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.903563] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.903570] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.903586] sas: broadcast received: 0 [ 1005.903611] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.905387] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.905388] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.905404] sas: broadcast received: 0 [ 1005.905429] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.907161] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.907168] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.907182] sas: broadcast received: 0 [ 1005.907207] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.908944] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.908946] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.909025] sas: broadcast received: 0 [ 1005.909062] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.910912] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.910919] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.910947] sas: broadcast received: 0 [ 1005.910985] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.912843] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.912847] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.912877] sas: broadcast received: 0 [ 1005.912911] sas: REVALIDATING DOMAIN on port 0, pid:8 [ 1005.915191] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.915198] sas: done REVALIDATING DOMAIN on port 0, pid:8, res 0x0 [ 1005.915221] sas: broadcast received: 0 [ 1005.915259] sas: REVALIDATING DOMAIN on port 0, pid:1170 [ 1005.917957] sas: ex 570fd45f9d17b01f phys DID NOT change [ 1005.917965] sas: done REVALIDATING DOMAIN on port 0, pid:1170, res 0x0 [ 1005.920337] sd 4:0:11:0: [sdl] Attached SCSI disk [ 1005.921692] sd 4:0:4:0: [sde] Attached SCSI disk [ 1008.107610] hisi_sas_v3_hw :b4:02.0: 16 hw queues [ 1008.112712] scsi host6: hisi_sas_v3_hw [ 1010.428061] hisi_sas_v3_hw :b4:04.0: 16 hw queues [ 1010.433120] scsi host7: hisi_sas_v3_hw root@ubuntu:/sys/kernel/debug/hisi_sas/:74:02.0# [Expected Results] Recurrence Logs： [ 360.441633] SET = 0, FnV = 0 [ 360.444689] EA = 0, S1PTW = 0 [ 360.447863] Data abort info: [ 360.450783] ISV = 0, ISS = 0x0044 [ 360.454663] CM = 0, WnR = 1 [ 360.457673] user pgtable: 4k pages, 48-bit VAs, pgdp=00211b7ae000 [ 360.464140] [] pgd=, p4d= [ 360.470969] Internal error: Oops: 9644 [#2] SMP [ 360.475844] Modules linked in: hisi_sas_v3_hw hisi_sas_main nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif joydev input_leds efi_pstore arm_spe_pmu hisi_hpre ecdh_generic libcurve25519_generic hns_roce_hw_v2 ecc hisi_zip uio_pdrv
[Kernel-packages] [Bug 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic
no longer priority ** Changed in: oem-priority Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic Status in OEM Priority Project: Won't Fix Status in OEM Priority Project bionic series: Won't Fix Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem source package in Bionic: Confirmed Bug description: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968488] Re: mpv crashes when run on wayland session on nvidia/intel (optimus) system when prime-select is on-demand
** Changed in: mpv (Ubuntu) Status: Confirmed => Fix Released ** Package changed: mpv (Ubuntu) => egl-wayland (Ubuntu) ** Tags added: fixed-in-1.1.10 fixed-upstream ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to egl-wayland in Ubuntu. https://bugs.launchpad.net/bugs/1968488 Title: mpv crashes when run on wayland session on nvidia/intel (optimus) system when prime-select is on-demand Status in NVIDIA / egl-wayland: New Status in MPV: Fix Released Status in egl-wayland package in Ubuntu: Fix Released Bug description: (+) Video --vid=1 (*) (h264 640x480 29.970fps) (+) Audio --aid=1 --alang=eng (*) (opus 2ch 48000Hz) [vo/gpu/wayland] GNOME's wayland compositor lacks support for the idle inhibit protocol. This means the screen can blank during playback. AO: [pulse] 48000Hz stereo 2ch float VO: [gpu] 640x480 yuv420p [destroyed object]: error 7: failed to import supplied dmabufs: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a [vo/gpu/wayland] Error occurred on the display fd, closing Mpv crashes on system after running it when prime-select is on-demand If we set prime-select intel then it works. Seems to be same as https://github.com/mpv-player/mpv/issues/9393 as using the workaround in the issue fixes the issue (__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json) and seems to be fixed(?) in fedora in https://bodhi.fedoraproject.org/updates/FEDORA-2021-0526645c86 one more thing to note is that eglinfo by default shows nvidia but using the workaround makes it show Intel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mpv 0.34.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 10 21:32:14 2022 InstallationDate: Installed on 2022-03-13 (28 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220312) SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/egl-wayland/+bug/1968488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968488] [NEW] mpv crashes when run on wayland session on nvidia/intel (optimus) system when prime-select is on-demand
You have been subscribed to a public bug: (+) Video --vid=1 (*) (h264 640x480 29.970fps) (+) Audio --aid=1 --alang=eng (*) (opus 2ch 48000Hz) [vo/gpu/wayland] GNOME's wayland compositor lacks support for the idle inhibit protocol. This means the screen can blank during playback. AO: [pulse] 48000Hz stereo 2ch float VO: [gpu] 640x480 yuv420p [destroyed object]: error 7: failed to import supplied dmabufs: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a [vo/gpu/wayland] Error occurred on the display fd, closing Mpv crashes on system after running it when prime-select is on-demand If we set prime-select intel then it works. Seems to be same as https://github.com/mpv-player/mpv/issues/9393 as using the workaround in the issue fixes the issue (__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/50_mesa.json) and seems to be fixed(?) in fedora in https://bodhi.fedoraproject.org/updates/FEDORA-2021-0526645c86 one more thing to note is that eglinfo by default shows nvidia but using the workaround makes it show Intel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mpv 0.34.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 10 21:32:14 2022 InstallationDate: Installed on 2022-03-13 (28 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220312) SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: egl-wayland Importance: Unknown Status: New ** Affects: mpv Importance: Unknown Status: Fix Released ** Affects: egl-wayland (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: amd64 apport-bug intel jammy nvidia nvidia-wayland protocol-error wayland-session -- mpv crashes when run on wayland session on nvidia/intel (optimus) system when prime-select is on-demand https://bugs.launchpad.net/bugs/1968488 You received this bug notification because you are a member of Kernel Packages, which is subscribed to egl-wayland 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 1989809] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616307/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616308/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616305/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] Re: ssd does not start after suspend
i tried following commands but still same:acpiphp.disable=1 pcie_aspm=off and this is most probably a bug because there was no problem on 16.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616304/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616306/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616310/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616309/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616302/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616303/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616301/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616297/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616296/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616300/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616295/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616299/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616298/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616293/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616294/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616292/+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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-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/09/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.15 dmi.board.asset.tag: Tag 12345 dmi.board.name: P770ZM dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: P770ZM dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] Re: ssd does not start after suspend
apport information ** Tags added: apport-collected jammy ** Description changed: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: veysel 1346 F pulseaudio + /dev/snd/controlC1: veysel 1346 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: XFCE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-07-16 (62 days ago) + InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: Notebook P770ZM + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-41-generic N/A + linux-backports-modules-5.15.0-41-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.5 + Tags: jammy + Uname: Linux 5.15.0-41-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/09/2015 + dmi.bios.release: 4.6 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1.03.15 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: P770ZM + dmi.board.vendor: Notebook + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 9 + dmi.chassis.vendor: Notebook + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.15:bd06/09/2015:br4.6:svnNotebook:pnP770ZM:pvrNotApplicable:rvnNotebook:rnP770ZM:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:skuNotApplicable: + dmi.product.family: Not Applicable + dmi.product.name: P770ZM + dmi.product.sku: Not Applicable + dmi.product.version: Not Applicable + dmi.sys.vendor: Notebook ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1989809/+attachment/5616291/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: veysel 1346 F pulseaudio /dev/snd/controlC1: veysel 1346 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-16 (62 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Notebook P770ZM NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=UUID=95b7b217-96a1-45f9-abca-ed5a47a176c0 ro i8042.nomux=1 quiet splash acpiphp.disable=1 pcie_aspm=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-41-generi
[Kernel-packages] [Bug 1989809] Re: ssd does not start after suspend
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1989809 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. ** Package changed: ubuntu => linux (Ubuntu) ** 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/1989809 Title: ssd does not start after suspend Status in linux package in Ubuntu: Incomplete Bug description: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989809] [NEW] ssd does not start after suspend
You have been subscribed to a public bug: I have a ssd on my ubuntu 22.04. it has luks for /home folder. like it seems: Filesystem Size Used Avail Use% Mounted on tmpfs 1,6G 3,3M 1,6G 1% /run /dev/nvme0n1p8 147G 15G 125G 11% / tmpfs 7,8G 23M 7,8G 1% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock /dev/nvme0n1p5 739M 250M 435M 37% /boot /dev/nvme0n1p1 96M 31M 66M 32% /boot/efi /dev/mapper/ubuntuvg-home 380G 22G 340G 6% /home tmpfs 1,6G 64K 1,6G 1% /run/user/1000 but after suspend I resumed computer and I get this error: ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 22.04 bot-comment ext4 luks ssd suspend -- ssd does not start after suspend https://bugs.launchpad.net/bugs/1989809 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 1870597] Re: libinput says "your system is too slow"
Please try Ubuntu 22.04 when you can because it is much faster: https://ubuntu.com/download/desktop -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in libinput: Fix Released Status in Linux: Confirmed Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1643978] Re: hv_set_ifconfig creates corrupt file for multiple interfaces
** Tags removed: hyperv -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1643978 Title: hv_set_ifconfig creates corrupt file for multiple interfaces Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: hv_set_ifconfig will create multiple GATEWAY entries in the interfaces file if there are multiple ethernet interfaces. This causes subsequent calls to ifup for the primary interface to fail with "RTNETLINK answers: File exists". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-cloud-tools-virtual-lts-xenial 4.4.0.47.50 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Nov 22 20:16 seq crw-rw+ 1 root audio 116, 33 Nov 22 20:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Nov 22 20:26:27 2016 HibernationDevice: RESUME=UUID=a3b32a0b-59a9-4b50-8d31-a06477933916 InstallationDate: Installed on 2016-11-22 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PciMultimedia: ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=31af956a-1342-4e8d-9c74-af0308e00111 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 1923-5120-7734-2680-0264-8714-27 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1646248] Re: Injecting DHCP configuration from Hyper-V host fails
** Tags removed: hyperv -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1646248 Title: Injecting DHCP configuration from Hyper-V host fails Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: When injecting a DHCP configuration from a Hyper-V host using WMI, the IP address does not change, and the syslog contains the following line: Failed to execute cmd 'hv_set_ifconfig /var/lib/hyperv/ifcfg-eth0'; error: 2 No such file or directory the ifcfg-eth0 exists with a modification time identical to the log line's. Switching the scheduler to noop did not resolve this issue. --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 1 10:06 seq crw-rw+ 1 root audio 116, 33 Dec 1 10:06 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a3b32a0b-59a9-4b50-8d31-a06477933916 InstallationDate: Installed on 2016-11-22 (8 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=31af956a-1342-4e8d-9c74-af0308e00111 ro ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 1923-5120-7734-2680-0264-8714-27 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 1 10:06 seq crw-rw+ 1 root audio 116, 33 Dec 1 10:06 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a3b32a0b-59a9-4b50-8d31-a06477933916 InstallationDate: Installed on 2016-11-22 (8 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=31af956a-1342-4e8d-9c74-af0308e00111 ro ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.5 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 1923-5120-7734-2680-0264-8714-27 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmerican
[Kernel-packages] [Bug 1813026] Re: [Hyper-V] VM console orphan newline input during login
** Tags removed: hyperv ** Tags added: hyper-v -- 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/1813026 Title: [Hyper-V] VM console orphan newline input during login Status in linux-azure package in Ubuntu: Confirmed Bug description: In Bionic azure-edge proposed kernel 4.18.0-1008 we're observing an issue that got carried from upstream. This is the first version we checked specifically for this issue, we don't have yet a good/bad proposed comparison set of versions. linux-next-5.0.0-9673b4a-20012019 does not have this issue <- daily upstream linux-next linux-next-4.20.0-6a1d293-27122018 has the issue <- all 4.1x/4.2x series from upstream have this problem. This behavior can be seen only on Hyper-V, as it must use the VM console UI: - boot the above kernels. - try to login with username and password. - After you input the username and press Enter in the Hyper-V console, another Enter (newline) is automatically received by the console, making it impossible to input the password. Afterward, the console behaves like a series of newlines are received and it resets after a while, presenting again the linux user login. Repro rates: - 100% on WS2019 - on WS2016 depending on situation it might not be visible 100%. Problem does not exist for Azure, it's specific to Hyper-V VM console only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1898395] Re: [nvidia] [amdgpu] Problem with external monitor
** Tags removed: multi-gpu ** Tags added: multigpu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1898395 Title: [nvidia] [amdgpu] Problem with external monitor Status in nvidia-graphics-drivers-450 package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: So, I installed Ubuntu 20.04 on my laptop with Ryzen 7 4800h processor and Nvidia gtx 1650 graphic card.. But i wasn't able to make my external monitor work.. At first it wasn't even recognized, but after I updated kernel to version 5.7.1 and with(only with latest) nvidia drivers 450 it recognized external monitor and I get options when I press SUPER KEY + P that I can switch screens.. But even though I pick external monitor and I see that it switch to it, monitor is turned on, but I have only black screen and can't do anything.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.7.1-050701-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 22:59:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.7.1-050701-generic, x86_64: installed nvidia, 450.66, 5.7.1-050701-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3a43] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3a3f] InstallationDate: Installed on 2020-09-15 (18 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 82B5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.1-050701-generic root=UUID=29bfdbd7-583f-4a6e-8e15-9bf5e33c383d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1898395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833744] Re: [Hyper-V] pick-up hv_netvsc commit in linux-azure 4.15
** Tags removed: hyperv ** Tags added: hyper-v -- 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/1833744 Title: [Hyper-V] pick-up hv_netvsc commit in linux-azure 4.15 Status in linux-azure package in Ubuntu: Confirmed Bug description: Please include this missing commit. We need it in the Xenial 16.04 linux-azure kernel series 4.15. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=273de02ae7d828d72d66eb5fce181e1f3f96d0cd hv_netvsc: Add handlers for ethtool get/set msg level The handlers for ethtool get/set msg level are missing from netvsc. This patch adds them. Signed-off-by: Haiyang Zhang Signed-off-by: David S. Miller da...@davemloft.net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1833744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986713] Re: azure: Replace hyperv_fb with hyperv_drm
** Tags removed: hyperv ** Tags added: hyper-v -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986713 Title: azure: Replace hyperv_fb with hyperv_drm Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification [Impact] Microsoft has asked to replace hyperv_fb with hyperv_drm in linux- modules-azure. [Test Plan] Extract linux-modules and ensure hyperv_drm.ko exists and hyperv_fb.ko does not. [Where things could go wrong] According to Microsoft, hyperv_drm is a direct replacement for hyperv_fb, yet there could be cases where hyperv_fb is being explicitly installed by customized images. [Other Info] SF: #00342707 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] Re: [Hyper-V] Login screen does not appear
** Tags removed: hyperv ** Tags added: hyper-v -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1979321] Re: linux-intel 5.13 to 5.15 transition
This bug was fixed in the package linux-meta-intel-iotg-5.15 - 5.15.0.1015.20~20.04.10 --- linux-meta-intel-iotg-5.15 (5.15.0.1015.20~20.04.10) focal; urgency=medium * Bump ABI 5.15.0-1015.20~20.04 linux-meta-intel-iotg-5.15 (5.15.0.1014.18~20.04.9) focal; urgency=medium * Bump ABI 5.15.0-1014.18~20.04 * Packaging resync (LP: #1786013) - [Packaging] update variants - [Packaging] resync debian/dkms-versions from main package * linux-intel 5.13 to 5.15 transition (LP: #1979321) - [Packaging] Add transitional packages for linux-intel-5.13 -- Philip Cox Fri, 02 Sep 2022 08:44:22 -0400 ** Changed in: linux-meta-intel-iotg-5.15 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979321 Title: linux-intel 5.13 to 5.15 transition Status in linux package in Ubuntu: Invalid Status in linux-meta-intel-iotg-5.15 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-meta-intel-iotg-5.15 source package in Focal: Fix Released Bug description: intel iotg kernel transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989820] [NEW] package nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-515 package post-installation script subprocess returned error
Public bug reported: I completed the installation on both 20.04.3, allowing it to auto-update to 20.04.5 during the install, and install third-party. None of the nvidia-driver-xxx packages would complete install. I did a complete format install to 22.04.1, with no third-party during the install (it would crash the installer, and not complete, if I allowed third-party). After the installation completed, I allowed all packages to update fully: sudo apt update sudo apt upgrade *reboot* Then installed broadcom wifi proprietary, and enabled Secure Boot *reboot* Enrolled MOK password *reboot* Then I pulled back up a terminal, to see any errors line by line. sudo apt install nvidia-driver-515 It downloaded 1.2 gigs of information. Spit out error code again, same as 20.04.x ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 15 17:39:57 2022 ErrorMessage: installed nvidia-dkms-515 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-09-15 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: nvidia-graphics-drivers-515 Title: package nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-515 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1989820 Title: package nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-515 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: I completed the installation on both 20.04.3, allowing it to auto-update to 20.04.5 during the install, and install third-party. None of the nvidia-driver-xxx packages would complete install. I did a complete format install to 22.04.1, with no third-party during the install (it would crash the installer, and not complete, if I allowed third-party). After the installation completed, I allowed all packages to update fully: sudo apt update sudo apt upgrade *reboot* Then installed broadcom wifi proprietary, and enabled Secure Boot *reboot* Enrolled MOK password *reboot* Then I pulled back up a terminal, to see any errors line by line. sudo apt install nvidia-driver-515 It downloaded 1.2 gigs of information. Spit out error code again, same as 20.04.x ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Sep 15 17:39:57 2022 ErrorMessage: installed nvidia-dkms-515 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-09-15 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: nvidia-graphics-drivers-515 Title: package nvidia-dkms-515 515.65.01-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-515 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1989820/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870597] Re: libinput says "your system is too slow"
The problem come back again after recent updates in ubuntu 20.04. System is stuttering when moving mouse and typing on keyboard: mutter3.36.9-0ubuntu0.20.04.2 xserver-xorg-input-libinput 0.29.0-1 libinput10:amd64 1.15.5-1ubuntu0.3 GNOME Shell 3.36.9 xorg-server 2:1.20.13-1ubuntu1~20.04.3 5.15.0-46-generic Lot of errors like following in journald: ``` /usr/lib/gdm3/gdm-x-session[4273]: (EE) client bug: timer event16 debounce short: scheduled expiry is in the past (-2ms), your system is too slow /usr/lib/gdm3/gdm-x-session[4273]: (EE) client bug: timer event16 debounce: scheduled expiry is in the past (-1ms), your system is too slow ``` Other DE does not have this 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/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in libinput: Fix Released Status in Linux: Confirmed Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989713] Re: Old start4.elf / fixup4.dat in 22.04
** Also affects: linux-firmware-raspi (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid ** Also affects: linux-firmware-raspi2 (Ubuntu) Importance: Undecided Status: New -- 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/1989713 Title: Old start4.elf / fixup4.dat in 22.04 Status in linux-firmware-raspi package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Status in linux-raspi package in Ubuntu: Invalid Bug description: Hi there, there is the issue connected with "Initramfs unpacking failed: Decoding failed" error during Ubuntu boot. See https://github.com/raspberrypi/firmware/issues/1746 and https://github.com/raspberrypi/firmware/issues/1731. The Raspberry Pi have the update for start4.elf / fixup4.dat with fix it. Could you please include update for these files in new ubuntu release ASAP? Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi/+bug/1989713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
“obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
`/var/cache/pbuilder/build/276481/build/grub2-2.06/obj/monolithic/grub-
efi-amd64/grubx64.efi`
* My build command: `sudo PBSHELL=1
[Kernel-packages] [Bug 1989625] Re: Bionic update: upstream stable patchset 2022-09-14
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989625 Title: Bionic update: upstream stable patchset 2022-09-14 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-09-14 Ported from the following upstream stable releases: v4.14.286, v4.19.250 v4.14.287, v4.19.251 v4.14.288, v4.19.252 v4.14.289, v4.19.253 from git://git.kernel.org/ random: schedule mix_interrupt_randomness() less often ata: libata: add qc->flags in ata_qc_complete_template tracepoint dm era: commit metadata in postsuspend after worker stops random: quiet urandom warning ratelimit suppression message USB: serial: option: add Telit LE910Cx 0x1250 composition USB: serial: option: add Quectel EM05-G modem USB: serial: option: add Quectel RM500K module support bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers x86/xen: Remove undefined behavior in setup_features() MIPS: Remove repetitive increase irq_err_count igb: Make DMA faster when CPU is active on the PCIe link iio: adc: vf610: fix conversion mode sysfs node name usb: chipidea: udc: check request status before setting device address iio:accel:bma180: rearrange iio trigger get and register iio: accel: mma8452: ignore the return value of reset operation iio: gyro: mpu3050: Fix the error handling in mpu3050_power_up() iio: trigger: sysfs: fix use-after-free on remove iio: adc: axp288: Override TS pin bias current for some models xtensa: xtfpga: Fix refcount leak bug in setup xtensa: Fix refcount leak bug in time.c powerpc: Enable execve syscall exit tracepoint powerpc/rtas: Allow ibm,platform-dump RTAS call with null buffer address powerpc/powernv: wire up rng during setup_arch ARM: dts: imx6qdl: correct PU regulator ramp delay ARM: exynos: Fix refcount leak in exynos_map_pmu ARM: Fix refcount leak in axxia_boot_secondary ARM: cns3xxx: Fix refcount leak in cns3xxx_init modpost: fix section mismatch check for exported init/exit sections powerpc/pseries: wire up rng during setup_arch() drm: remove drm_fb_helper_modinit xen: unexport __init-annotated xen_xlate_map_ballooned_pages() fdt: Update CRC check for rng-seed kexec_file: drop weak attribute from arch_kexec_apply_relocations[_add] swiotlb: skip swiotlb_bounce when orig_addr is zero net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms afs: Fix dynamic root getattr iio:chemical:ccs811: rearrange iio trigger get and register soc: bcm: brcmstb: pm: pm-arm: Fix refcount leak in brcmstb_pm_probe UBUNTU: Upstream stable to v4.14.286, v4.19.250 nvdimm: Fix badblocks clear off-by-one error dm raid: fix accesses beyond end of raid member array dm raid: fix KASAN warning in raid5_add_disks s390/archrandom: simplify back to earlier design and initialize earlier SUNRPC: Fix READ_PLUS crasher net: rose: fix UAF bugs caused by timer handler net: usb: ax88179_178a: Fix packet receiving RDMA/qedr: Fix reporting QP timeout attribute usbnet: fix memory allocation in helpers net: ipv6: unexport __init-annotated seg6_hmac_net_init() caif_virtio: fix race between virtio_device_ready() and ndo_open() netfilter: nft_dynset: restore set element counter when failing to update net: bonding: fix possible NULL deref in rlb code net: bonding: fix use-after-free after 802.3ad slave unbind nfc: nfcmrvl: Fix irq_of_parse_and_map() return value NFC: nxp-nci: Don't issue a zero length i2c_master_read() xen/gntdev: Avoid blocking in unmap_grant_pages() hwmon: (ibmaem) don't call platform_device_del() if platform_device_add() fails sit: use min ipv6/sit: fix ipip6_tunnel_get_prl return value net: Rename and export copy_skb_header xen/blkfront: fix leaking data in shared pages xen/netfront: fix leaking data in shared pages xen/netfront: force data bouncing when backend is untrusted xen/blkfront: force data bouncing when backend is untrusted xen/arm: Fix race in RB-tree based P2M accounting net: usb: qmi_wwan: add Telit 0x1060 composition net: usb: qmi_wwan: add Telit 0x1070 composition virtio-net: fix race between ndo_open() and virt
[Kernel-packages] [Bug 1701297] Re: NTP reload failure (unable to read library) on overlayfs
** Changed in: cloud-init (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1701297 Title: NTP reload failure (unable to read library) on overlayfs Status in cloud-init: Won't Fix Status in apparmor package in Ubuntu: Invalid Status in cloud-init package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Bug description: After update [1] of cloud-init in Ubuntu (which landed in xenial- updates on 2017-06-27), it is causing NTP reload failures. https://launchpad.net/ubuntu/+source/cloud- init/0.7.9-153-g16a7302f-0ubuntu1~16.04.1 In MAAS scenarios, this is causing the machine to fail to deploy. Related bugs: * bug 1645644: cloud-init ntp not using expected servers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1701297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989745] 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/1989745 Title: UBSAN array out of bounds in elantech.c Status in linux package in Ubuntu: Confirmed Bug description: The following crash occurred on my system, after it the touchpad was unusable. I've attached the related journalctl entries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aron 4404 F pulseaudio /dev/snd/pcmC0D0c: aron 4404 F...m pulseaudio /dev/snd/pcmC0D0p: aron 4404 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 15 18:08:22 2022 InstallationDate: Installed on 2021-03-18 (545 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20EMS01P00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=e5ebfacd-7758-4a10-9fe6-da38dc6615ef ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-07-28 (48 days ago) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20EMS01P00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20EMS01P00:pvrThinkPadYoga460:rvnLENOVO:rn20EMS01P00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EM_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20EMS01P00 dmi.product.sku: LENOVO_MT_20EM_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] Re: [Hyper-V] Login screen does not appear
I had also tried to disable Wayland in the display manager configuration file to see if there was an incompatibility there, however, I just ended up with the same result. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989745] [NEW] UBSAN array out of bounds in elantech.c
Public bug reported: The following crash occurred on my system, after it the touchpad was unusable. I've attached the related journalctl entries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aron 4404 F pulseaudio /dev/snd/pcmC0D0c: aron 4404 F...m pulseaudio /dev/snd/pcmC0D0p: aron 4404 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 15 18:08:22 2022 InstallationDate: Installed on 2021-03-18 (545 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20EMS01P00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=e5ebfacd-7758-4a10-9fe6-da38dc6615ef ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-07-28 (48 days ago) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20EMS01P00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20EMS01P00:pvrThinkPadYoga460:rvnLENOVO:rn20EMS01P00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EM_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20EMS01P00 dmi.product.sku: LENOVO_MT_20EM_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/bugs/1989745/+attachment/5616145/+files/journalctl.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/1989745 Title: UBSAN array out of bounds in elantech.c Status in linux package in Ubuntu: New Bug description: The following crash occurred on my system, after it the touchpad was unusable. I've attached the related journalctl entries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-47-generic 5.15.0-47.51 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aron 4404 F pulseaudio /dev/snd/pcmC0D0c: aron 4404 F...m pulseaudio /dev/snd/pcmC0D0p: aron 4404 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 15 18:08:22 2022 InstallationDate: Installed on 2021-03-18 (545 days ago) InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20EMS01P00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=e5ebfacd-7758-4a10-9fe6-da38dc6615ef ro quiet splash systemd.unified_cgroup_hierarchy=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-07-28 (48 days ago) dmi.bios.date: 05/14/2019 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: R05ET81W (1.59) dmi.board.asset.tag: Not Available dmi.board.name: 20EMS01P00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20EMS01P00:pvrThinkPadYoga460:rvnLENOVO:rn20EMS01P00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EM_BU_Think_FM_ThinkPadYoga460: dmi.product.family: ThinkPad Yoga 460 dmi.product.name: 20EMS01P00 dmi.product.sku: LENOVO_MT_20EM_BU_Think_FM_ThinkPad Yoga 460 dmi.product.version: ThinkPad Yoga 460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989745/+subscriptions -- Mailing list: https://launchpa
[Kernel-packages] [Bug 1989649] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616120/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616117/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616114/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616119/+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/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616113/+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/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616116/+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/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616118/+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/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616115/+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/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616111/+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/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616112/+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/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616110/+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/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: Tags: jammy Uname: Linux 5.15.0-47-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: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] Re: [Hyper-V] Login screen does not appear
apport information ** Tags added: apport-collected ** Description changed: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-09-13 (1 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + + eth1 no wireless extensions. + Lspci: + + Lspci-vt: -[:00]- + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: + + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: Microsoft Corporation Virtual Machine + Package: linux (not installed) + ProcFB: 0 hyperv_fb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-47-generic N/A + linux-backports-modules-5.15.0-47-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.5 + RfKill: + + Tags: jammy + Uname: Linux 5.15.0-47-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: 11/01/2019 + dmi.bios.release: 4.0 + dmi.bios.vendor: Microsoft Corporation + dmi.bios.version: Hyper-V UEFI Release v4.0 + dmi.board.asset.tag: None + dmi.board.name: Virtual Machine + dmi.board.vendor: Microsoft Corporation + dmi.board.version: Hyper-V UEFI Release v4.0 + dmi.chassis.asset.tag: 3967-3183-5948-8629-1199-2464-54 + dmi.chassis.type: 3 + dmi.chassis.vendor: Microsoft Corporation + dmi.chassis.version: Hyper-V UEFI Release v4.0 + dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: + dmi.product.family: Virtual Machine + dmi.product.name: Virtual Machine + dmi.product.sku: None + dmi.product.version: Hyper-V UEFI Release v4.0 + dmi.sys.vendor: Microsoft Corporation ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1989649/+attachment/5616109/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Confirmed Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-releas
[Kernel-packages] [Bug 1981883] Re: amdgpu module crash after 5.15 kernel update
** Description changed: + [SRU Justification] + + Impact: The 5.15 kernel series introduced a regression compared to 5.13 + related to virtual display code on AMD GPUs. This causes crashes for + cloud/VM users back to Focal (using rolling cloud or HWE kernels). + + Fix: Upstream stable 5.15.61 contains a fix for this which is only + needed there since later kernel version have that code rewritten again. + This change would get picked up normally in the next stable cycle after + 2022.09.19. But given the impact we would apply the following patch from + 5.15.61 ahead of time: + + commit 27f8f5219fe4658537ba28fd01657e1062ac3960 linux-5.15.y + "drm/amdgpu: fix check in fbdev init" + + Test case: Booting the affected kernel on a VM which passes through AMD + GPU hardware. + + Regression potential: Worst case some driver functions will not get + disabled where they did before. + + --- original description --- + The kernel 5.15 amdgpu module crashes on load with a “BUG: kernel NULL pointer dereference” on Amazon EC2 G4ad hardware (custom AMD Radeon V520 Pro datacenter GPU) on focal (HWE) and jammy with kernel 5.15.0-1011 and possibly earlier, up through latest (revision 1015.19). This crash bug did not exist in any of the focal HWE 5.13 kernels. This is probably an upstream kernel bug, but I am also filing it here because existing focal users on EC2 will suddenly stop having access to their AMD GPUs after a reboot once the new 5.15 HWE kernel is installed. The full backtrace from dmesg is below. The offending function call which crashes in the 5.15 kernel corresponds to this source (sorry, not the right source tree, but the same driver) https://github.com/torvalds/linux/blob/8bb7eca972ad531c9b149c0a51ab43a417385813/drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c#L345 A workaround that I have discovered is adding “options amdgpu virtual_display=;” to a new modprobe.d configuration file - something which shouldn’t be required, but is at least harmless. - Here is the relevant BUG message and backtrace from dmesg: [ 318.111721] BUG: kernel NULL pointer dereference, address: [ 318.115443] #PF: supervisor instruction fetch in kernel mode [ 318.118443] #PF: error_code(0x0010) - not-present page [ 318.121177] PGD 0 P4D 0 [ 318.122688] Oops: 0010 [#1] SMP NOPTI [ 318.124592] CPU: 6 PID: 13667 Comm: modprobe Tainted: GW 5.15.0-1015-aws #19~20.04.1-Ubuntu [ 318.129711] Hardware name: Amazon EC2 g4ad.2xlarge/, BIOS 1.0 10/16/2017 [ 318.133167] RIP: 0010:0x0 [ 318.134704] Code: Unable to access opcode bytes at RIP 0xffd6. [ 318.138291] RSP: 0018:9841828d78e0 EFLAGS: 00010246 [ 318.140938] RAX: RBX: 8a4f16ae8000 RCX: 0001 [ 318.144604] RDX: RSI: 0003 RDI: 8a4f16ae8000 [ 318.148319] RBP: 9841828d7908 R08: 8a4f02460278 R09: 8a4f06422c40 [ 318.152151] R10: c01c42494f8a R11: 8a4f01dcb5b8 R12: 8a4f024602e8 [ 318.155929] R13: c107e4a0 R14: R15: 8a4f02460010 [ 318.159685] FS: 7f8afdc1c740() GS:8a55f098() knlGS: [ 318.163897] CS: 0010 DS: ES: CR0: 80050033 [ 318.167038] CR2: ffd6 CR3: 00011817e000 CR4: 003506e0 [ 318.170758] Call Trace: [ 318.173964] [ 318.176822] __drm_helper_disable_unused_functions+0xe7/0x100 [drm_kms_helper] [ 318.184230] drm_helper_disable_unused_functions+0x44/0x50 [drm_kms_helper] [ 318.189761] amdgpu_fbdev_init+0x104/0x110 [amdgpu] [ 318.194264] amdgpu_device_init.cold+0x7cc/0xc48 [amdgpu] [ 318.199061] ? pci_read_config_byte+0x27/0x40 [ 318.203206] amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] [ 318.207901] amdgpu_pci_probe+0x1ea/0x290 [amdgpu] [ 318.212445] local_pci_probe+0x4b/0x90 [ 318.216386] pci_device_probe+0x182/0x1f0 [ 318.220407] really_probe.part.0+0xcb/0x370 [ 318.224460] really_probe+0x40/0x80 [ 318.228232] __driver_probe_device+0x115/0x190 [ 318.232412] driver_probe_device+0x23/0xa0 [ 318.236436] __driver_attach+0xbd/0x160 [ 318.240348] ? __device_attach_driver+0x110/0x110 [ 318.244637] bus_for_each_dev+0x7e/0xc0 [ 318.248570] driver_attach+0x1e/0x20 [ 318.252474] bus_add_driver+0x161/0x200 [ 318.256412] driver_register+0x74/0xd0 [ 318.260332] __pci_register_driver+0x68/0x70 [ 318.264496] amdgpu_init+0x7c/0x1000 [amdgpu] [ 318.268841] ? 0xc146e000 [ 318.272521] do_one_initcall+0x48/0x1d0 [ 318.276446] ? __cond_resched+0x19/0x30 [ 318.280378] ? kmem_cache_alloc_trace+0x15a/0x420 [ 318.284736] do_init_module+0x52/0x230 [ 318.288644] load_module+0x1372/0x1600 [ 318.292529] __do_sys_finit_module+0xbf/0x120 [ 318.296706] ? __do_sys_finit_module+0xbf/0x120 [ 318.300947] __x64_sys_finit_module+0x1a/0x20 [ 318.305
[Kernel-packages] [Bug 1981883] Re: amdgpu module crash after 5.15 kernel update
** Package changed: linux-aws-5.15 (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981883 Title: amdgpu module crash after 5.15 kernel update Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Bug description: The kernel 5.15 amdgpu module crashes on load with a “BUG: kernel NULL pointer dereference” on Amazon EC2 G4ad hardware (custom AMD Radeon V520 Pro datacenter GPU) on focal (HWE) and jammy with kernel 5.15.0-1011 and possibly earlier, up through latest (revision 1015.19). This crash bug did not exist in any of the focal HWE 5.13 kernels. This is probably an upstream kernel bug, but I am also filing it here because existing focal users on EC2 will suddenly stop having access to their AMD GPUs after a reboot once the new 5.15 HWE kernel is installed. The full backtrace from dmesg is below. The offending function call which crashes in the 5.15 kernel corresponds to this source (sorry, not the right source tree, but the same driver) https://github.com/torvalds/linux/blob/8bb7eca972ad531c9b149c0a51ab43a417385813/drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c#L345 A workaround that I have discovered is adding “options amdgpu virtual_display=;” to a new modprobe.d configuration file - something which shouldn’t be required, but is at least harmless. Here is the relevant BUG message and backtrace from dmesg: [ 318.111721] BUG: kernel NULL pointer dereference, address: [ 318.115443] #PF: supervisor instruction fetch in kernel mode [ 318.118443] #PF: error_code(0x0010) - not-present page [ 318.121177] PGD 0 P4D 0 [ 318.122688] Oops: 0010 [#1] SMP NOPTI [ 318.124592] CPU: 6 PID: 13667 Comm: modprobe Tainted: GW 5.15.0-1015-aws #19~20.04.1-Ubuntu [ 318.129711] Hardware name: Amazon EC2 g4ad.2xlarge/, BIOS 1.0 10/16/2017 [ 318.133167] RIP: 0010:0x0 [ 318.134704] Code: Unable to access opcode bytes at RIP 0xffd6. [ 318.138291] RSP: 0018:9841828d78e0 EFLAGS: 00010246 [ 318.140938] RAX: RBX: 8a4f16ae8000 RCX: 0001 [ 318.144604] RDX: RSI: 0003 RDI: 8a4f16ae8000 [ 318.148319] RBP: 9841828d7908 R08: 8a4f02460278 R09: 8a4f06422c40 [ 318.152151] R10: c01c42494f8a R11: 8a4f01dcb5b8 R12: 8a4f024602e8 [ 318.155929] R13: c107e4a0 R14: R15: 8a4f02460010 [ 318.159685] FS: 7f8afdc1c740() GS:8a55f098() knlGS: [ 318.163897] CS: 0010 DS: ES: CR0: 80050033 [ 318.167038] CR2: ffd6 CR3: 00011817e000 CR4: 003506e0 [ 318.170758] Call Trace: [ 318.173964] [ 318.176822] __drm_helper_disable_unused_functions+0xe7/0x100 [drm_kms_helper] [ 318.184230] drm_helper_disable_unused_functions+0x44/0x50 [drm_kms_helper] [ 318.189761] amdgpu_fbdev_init+0x104/0x110 [amdgpu] [ 318.194264] amdgpu_device_init.cold+0x7cc/0xc48 [amdgpu] [ 318.199061] ? pci_read_config_byte+0x27/0x40 [ 318.203206] amdgpu_driver_load_kms+0x1e/0x270 [amdgpu] [ 318.207901] amdgpu_pci_probe+0x1ea/0x290 [amdgpu] [ 318.212445] local_pci_probe+0x4b/0x90 [ 318.216386] pci_device_probe+0x182/0x1f0 [ 318.220407] really_probe.part.0+0xcb/0x370 [ 318.224460] really_probe+0x40/0x80 [ 318.228232] __driver_probe_device+0x115/0x190 [ 318.232412] driver_probe_device+0x23/0xa0 [ 318.236436] __driver_attach+0xbd/0x160 [ 318.240348] ? __device_attach_driver+0x110/0x110 [ 318.244637] bus_for_each_dev+0x7e/0xc0 [ 318.248570] driver_attach+0x1e/0x20 [ 318.252474] bus_add_driver+0x161/0x200 [ 318.256412] driver_register+0x74/0xd0 [ 318.260332] __pci_register_driver+0x68/0x70 [ 318.264496] amdgpu_init+0x7c/0x1000 [amdgpu] [ 318.268841] ? 0xc146e000 [ 318.272521] do_one_initcall+0x48/0x1d0 [ 318.276446] ? __cond_resched+0x19/0x30 [ 318.280378] ? kmem_cache_alloc_trace+0x15a/0x420 [ 318.284736] do_init_module+0x52/0x230 [ 318.288644] load_module+0x1372/0x1600 [ 318.292529] __do_sys_finit_module+0xbf/0x120 [ 318.296706] ? __do_sys_finit_module+0xbf/0x120 [ 318.300947] __x64_sys_finit_module+0x1a/0x20 [ 318.305265] do_syscall_64+0x5c/0xc0 [ 318.308984] ? do_syscall_64+0x69/0xc0 [ 318.312841] ? do_syscall_64+0x69/0xc0 [ 318.316693] ? do_syscall_64+0x69/0xc0 [ 318.320545] entry_
[Kernel-packages] [Bug 1989483] Re: Installation error on Ubuntu 22.10
Correction: the build date on the file was 8/29/22 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989483 Title: Installation error on Ubuntu 22.10 Status in linux package in Ubuntu: Confirmed Bug description: Getting install "error installing linux-modules- nvidia-390-5.15.0.27-generic" on both daily build 9/12/22 and 9/13/22. Popup message; Post installation script subprocess returned error exit status 1 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2053 F wireplumber /dev/snd/seq:ubuntu 2051 F pipewire CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.473 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 13 15:29:05 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: CLEVO CO. W35_37ET ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220819.git8413c63c-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: W35_37ET dmi.board.vendor: CLEVO CO. dmi.board.version: N/A dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: CLEVO CO. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: W35_37ET dmi.product.sku: To be filled by O.E.M. dmi.product.version: N/A dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param
This is a grub bug and it is being tracked here: [SRU] unable to boot guest with large memory when SEV is enabled on host https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1989446 ** Changed in: grub2 (Ubuntu) Status: Confirmed => Invalid ** Changed in: grub2 (Ubuntu Impish) Status: Confirmed => Invalid ** Changed in: grub2 (Ubuntu Jammy) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1955655 Title: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param Status in grub2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in grub2 source package in Impish: Invalid Status in linux source package in Impish: Invalid Status in grub2 source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Bug description: While investigating LP: #1955395 by using the -generic kernel image, it appeared that it is impossible to boot the kernel unless the boot parameter swiotlb is set to 512M (swiotlb=262144). Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb it fails and later trigger a kernel panic with the following trace : $ grep TLB /tmp/console.log [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB [0.034219] kvm-guest: KVM setup pv remote TLB flush [0.037063] software IO TLB: Cannot allocate buffer [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [1.019552] software IO TLB: No low mem [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer ]--- The SWIOTLB adjustment comes from the following kernel commit : https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12 For some reason, the LowMem allocation fails (as seen by the "software IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be completed. When booting with the swiotlb=262144 value, we get the following output : $ grep TLB /tmp/console.log [0.050908] kvm-guest: KVM setup pv remote TLB flush [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [1.071837] software IO TLB: mapped [mem 0x5bebe000-0x7bebe000] (512MB) [1.529804] software IO TLB: Memory encryption is active and system is using DMA bounce buffers For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without the need to set the swiotlb= value at boot time. The SWIOTLB buffer adjustment has been introduced in kernel 5.11. We can make SEV enabled resources available for testing if needed. ...Louis --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 23 13:32 seq crw-rw 1 root audio 116, 33 Dec 23 13:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Scaleway SCW-ENT1-S Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 swiotlb=262144 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic
[Kernel-packages] [Bug 1983625] Re: 5.15.0-1013-oracle: Unable to boot large memory SEV guest without setting swiotlb parameter.
This is a grub bug and it is being tracked here: [SRU] unable to boot guest with large memory when SEV is enabled on host https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1989446 ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983625 Title: 5.15.0-1013-oracle: Unable to boot large memory SEV guest without setting swiotlb parameter. Status in linux package in Ubuntu: Invalid Bug description: When launching a SEV Ubuntu22.04 guest with e.g. memory > 16876M, Ubuntu kernel 5.15.0-1013-oracle panics unless swiotlb=262144 is specified on guest kernel parameters. It seems that the kernel tries to adjust swiotlb buffer size but can not do that and crashes. With a memory size such as 8G, the guest boots fine. HOST INFO Host type : OCI Bare-Metal Server Server/Machine: ORACLE SERVER E2-2c CPU model : AMD EPYC 7742 64-Core Processor Architecture : x86_64 Hostname : atanveer-amd-sme OS: Oracle Linux Server release 7.9 Kernel: 5.4.17-2136.309.4.el7uek.x86_64 #2 SMP Tue Jun 28 17:35:13 PDT 2022 Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-18.oci.el7) OVMF/AAVMF: OVMF-1.6.3-1.el7.noarch Qemu command to launch SEV guest: /bin/qemu-system-x86_64 -name OL22.04-uefi \ -machine q35 \ -enable-kvm \ -cpu host,+host-phys-bits \ -m 16877M \ -smp 8,maxcpus=240 \ -D ./22.04-uefi.log \ -nodefaults \ -monitor stdio \ -vnc 0.0.0.0:0,to=999 \ -vga std \ -drive file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly \ -drive file=OVMF_VARS.pure-efi.fd.ol22.04,index=1,if=pflash,format=raw \ -device virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true \ -drive file=Ubuntu-22.04-2022.06.16-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk \ -device ide-hd,drive=local_disk0,id=local_disk1,bootindex=0 \ -qmp tcp:127.0.0.1:3334,server,nowait \ -serial telnet:127.0.0.1:,server,nowait \ -device virtio-rng-pci,disable-legacy=on,iommu_platform=true \ -object sev-guest,id=sev0,cbitpos=47,reduced-phys-bits=1 \ -machine memory-encryption=sev0 Console log: [0.005025] software IO TLB: SWIOTLB bounce buffer size adjusted to 1011MB [0.033881] kvm-guest: KVM setup pv remote TLB flush [0.054931] software IO TLB: Cannot allocate buffer [0.248933] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127 [0.249582] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0 [0.317440] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.317440] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [0.424952] iommu: DMA domain TLB invalidation policy: lazy mode [0.570923] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [0.571669] software IO TLB: No low mem . . . . [1.233515] ata1: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010100 irq 28 [1.234985] ata2: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010180 irq 28 [1.236464] ata3: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010200 irq 28 [1.237863] ata4: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010280 irq 28 [1.239257] ata5: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010300 irq 28 [1.240659] ata6: SATA max UDMA/133 abar m4096@0xc101 port 0xc1010380 irq 28 [1.555165] ata5: SATA link down (SStatus 0 SControl 300) [1.556661] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [1.558232] ata2: SATA link down (SStatus 0 SControl 300) [1.559728] ata4: SATA link down (SStatus 0 SControl 300) [1.560996] ata3: SATA link down (SStatus 0 SControl 300) [1.562134] ata1: SATA link down (SStatus 0 SControl 300) [1.563566] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [6.911450] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [6.912906] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 12.288045] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 12.289904] ata6.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 17.663548] ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 242.883993] INFO: task kworker/u480:0:9 blocked for more than 120 seconds. [ 242.885619] Not tainted 5.15.0-1013-oracle #17-Ubuntu [ 242.886743] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.888198] task:kworker/u480:0 state:D stack:0 pid:9 ppid: 2 flags:0x4000 [ 242.889703] Workqueue: events_unbound async_run_entry_fn [ 242.890882] Call Trace: [ 242.891727] Full console log is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+so
[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
** Tags added: oem-priority originate-from-1980039 stella ** Tags added: originate-from-1955958 ** Tags added: originate-from-1970734 ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: Kai-Heng Feng (kaihengfeng) Status: Confirmed ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided => Medium ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) 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/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.17 source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1989713] [NEW] Old start4.elf / fixup4.dat in 22.04
Public bug reported: Hi there, there is the issue connected with "Initramfs unpacking failed: Decoding failed" error during Ubuntu boot. See https://github.com/raspberrypi/firmware/issues/1746 and https://github.com/raspberrypi/firmware/issues/1731. The Raspberry Pi have the update for start4.elf / fixup4.dat with fix it. Could you please include update for these files in new ubuntu release ASAP? Thanks in advance! ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- 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/1989713 Title: Old start4.elf / fixup4.dat in 22.04 Status in linux-raspi package in Ubuntu: New Bug description: Hi there, there is the issue connected with "Initramfs unpacking failed: Decoding failed" error during Ubuntu boot. See https://github.com/raspberrypi/firmware/issues/1746 and https://github.com/raspberrypi/firmware/issues/1731. The Raspberry Pi have the update for start4.elf / fixup4.dat with fix it. Could you please include update for these files in new ubuntu release ASAP? Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1989713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989705] [NEW] SIGNEDv3: add a linux-generate ancillary package
Public bug reported: Add a new linux-generate package as an ancillary package. This allows us to avoid publishing the custom signing tarballs into the archive, which in turn helps ensure we never sign a kernel with an inappropriate key. ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1989705 Title: SIGNEDv3: add a linux-generate ancillary package Status in linux-signed package in Ubuntu: New Bug description: Add a new linux-generate package as an ancillary package. This allows us to avoid publishing the custom signing tarballs into the archive, which in turn helps ensure we never sign a kernel with an inappropriate key. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1989705/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981699] Re: ubuntu_ltp.mm:thp02 times out on with 5.15 kernels on arm64 64k pages
*** This bug is a duplicate of bug 1989529 *** https://bugs.launchpad.net/bugs/1989529 ** This bug has been marked a duplicate of bug 1989529 mm/thp02 in ubuntu_ltp failed on node starmie-kernel with J-nvidia-64k -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981699 Title: ubuntu_ltp.mm:thp02 times out on with 5.15 kernels on arm64 64k pages Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Bug description: The thp02 testcase from ubuntu_ltp.mm running on 5.15 kernels times out on some arm64 systems with 64k pages flavours. INFO: Test start time: Wed Jul 13 17:55:36 UTC 2022 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 205749 -n 205749 -f /tmp/ltp-gbCWODkS0Q/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_test.c:1524: TINFO: Timeout per run is 0h 00m 30s thp02.c:68: TINFO: mremap (0xfffe6000-0xfffedfff) to (0xfffdc000-0xfffe3fff) thp02.c:68: TINFO: mremap (0xfffe6000-0xfffedfff) to (0xfffdc001-0xfffe4000) thp02.c:68: TINFO: mremap (0xfffe6001-0xfffee000) to (0xfffdc000-0xfffe3fff) Test timeouted, sending SIGKILL! tst_test.c:1569: TINFO: Killed the leftover descendant processes tst_test.c:1575: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1577: TBROK: Test killed! (timeout?) For now found with the following combinations: - jammy/linux generic-64k on starmie-kernel - focal/linux-lowlatency-hwe-5.15 lowlatency-64k on starmie-kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1981699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989253] Re: Lenovo Thinkpad T14 G3 HDMI not working
@Timo I'm not sure if the traceback in the log is related to HDMI not being available. I get the same error at every boot, even when w/o HDMI connected, or when using an external monitor via USB-C (which works). Should I open a separate bug for this traceback or repurpose this one? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989253 Title: Lenovo Thinkpad T14 G3 HDMI not working Status in linux package in Ubuntu: Confirmed Bug description: On 22.10 with 5.19.0-15-generic on a ThinkPad T14 gen3 (intel-based), the HDMI port is not working, screen is not detected (both in xorg and wayland). Also tested with older 5.15.0-27-generic kernel, same result. I see the following traceback in dmesg: [3.510605] [ cut here ] [3.510615] i915 :00:02.0: drm_WARN_ON(intel_dp->pps.vdd_wakeref) [3.510663] WARNING: CPU: 8 PID: 263 at drivers/gpu/drm/i915/display/intel_pps.c:593 intel_pps_vdd_on_unlocked+0x276/0x290 [i915] [3.511147] Modules linked in: i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper cec rc_core drm_kms_helper syscopyarea sysfillrect hid_generic sysimgblt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel fb_sys_fops intel_lpss_pci i2c_hid_acpi aesni_intel nvme spi_intel_pci intel_lpss xhci_pci i2c_hid i2c_i801 drm crypto_simd psmouse e1000e thunderbolt nvme_core spi_intel i2c_smbus idma64 xhci_pci_renesas wmi hid cryptd video pinctrl_tigerlake [3.511228] CPU: 8 PID: 263 Comm: systemd-udevd Not tainted 5.19.0-15-generic #15-Ubuntu [3.511237] Hardware name: LENOVO 21AHCTO1WW/21AHCTO1WW, BIOS N3MET06W (1.03 ) 07/11/2022 [3.511241] RIP: 0010:intel_pps_vdd_on_unlocked+0x276/0x290 [i915] [3.511636] Code: 4c 8b 77 50 4d 85 f6 75 03 4c 8b 37 e8 43 8e 7e de 48 c7 c1 70 1a 97 c0 4c 89 f2 48 c7 c7 26 3a 94 c0 48 89 c6 e8 44 0e c8 de <0f> 0b e9 27 fe ff ff e8 5e 63 d3 de 66 66 2e 0f 1f 84 00 00 00 00 [3.511642] RSP: 0018:b6b6c0d3b380 EFLAGS: 00010282 [3.511649] RAX: RBX: 8a5f9d464170 RCX: a097b148 [3.511654] RDX: RSI: 0003 RDI: 0001 [3.511657] RBP: b6b6c0d3b3d8 R08: R09: a0fb5642 [3.511661] R10: R11: 03d7 R12: 8a5fa2788000 [3.511666] R13: R14: 8a5f82740a20 R15: 8a5fa27887e0 [3.511670] FS: 7ff53569d8c0() GS:8a6aaf60() knlGS: [3.511676] CS: 0010 DS: ES: CR0: 80050033 [3.511680] CR2: 55ae059d3140 CR3: 00011d7a2006 CR4: 00770ee0 [3.511686] PKRU: 5554 [3.511689] Call Trace: [3.511693] [3.511700] ? intel_display_power_get+0x56/0x70 [i915] [3.512087] intel_dp_aux_xfer+0x12c/0x860 [i915] [3.512427] ? raw_spin_rq_unlock+0x10/0x40 [3.512440] intel_dp_aux_transfer+0x1d0/0x2f0 [i915] [3.512757] drm_dp_dpcd_access+0xad/0x130 [drm_display_helper] [3.512791] drm_dp_dpcd_write+0xb2/0x100 [drm_display_helper] [3.512825] intel_dp_sink_set_decompression_state+0x86/0xd0 [i915] [3.513107] intel_disable_ddi+0x10b/0x1b0 [i915] [3.513391] intel_encoders_disable+0x9b/0xc0 [i915] [3.513699] hsw_crtc_disable+0x61/0x80 [i915] [3.513964] intel_old_crtc_state_disables+0x3d/0xb0 [i915] [3.514212] intel_commit_modeset_disables+0x2ab/0x330 [i915] [3.514465] ? modeset_get_crtc_power_domains+0x69/0xc0 [i915] [3.514707] intel_atomic_commit_tail+0x197/0xbb0 [i915] [3.514937] intel_atomic_commit+0x3b1/0x400 [i915] [3.515155] drm_atomic_commit+0x94/0xd0 [drm] [3.515231] ? drm_plane_create_color_properties.cold+0x45/0x45 [drm] [3.515320] intel_initial_commit+0x183/0x210 [i915] [3.515544] intel_modeset_init+0x22/0x80 [i915] [3.515765] i915_driver_probe+0x1ec/0x480 [i915] [3.515963] ? drm_privacy_screen_get+0x164/0x190 [drm] [3.516038] ? acpi_dev_found+0x64/0x70 [3.516046] i915_pci_probe+0x56/0x140 [i915] [3.516245] local_pci_probe+0x44/0x80 [3.516251] pci_call_probe+0x55/0x180 [3.516255] pci_device_probe+0x84/0x110 [3.516260] really_probe+0x1ce/0x3a0 [3.516267] __driver_probe_device+0x11b/0x190 [3.516272] driver_probe_device+0x24/0xd0 [3.516278] __driver_attach+0xd8/0x200 [3.516283] ? __device_attach_driver+0x120/0x120 [3.516289] bus_for_each_dev+0x79/0xc0 [3.516294] driver_attach+0x1e/0x30 [3.516299] bus_add_driver+0x178/0x220 [3.516304] driver_register+0x8f/0xf0 [3.516309] __pci_register_driver+0x62/0x70 [3.516313] i915_pci_register_driver+0x23/0x30 [i915] [3.516506] i915_init+0x3b/0xee [i915] [3.516706] ? 0xc0a2f000 [3.516710] do_one_initc
[Kernel-packages] [Bug 1989046] Re: support independent clock and LED GPIOs for Intel IPU6 platforms
** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => 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/1989046 Title: support independent clock and LED GPIOs for Intel IPU6 platforms Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] When migrated from power_ctrl_logic driver to int3472, two additional independent CLK/LED GPIOs other than powerdown/reset must be probed exceptionally. [Fix] Vendor provided patch in https://github.com/intel/ipu6-drivers/blob/2b8a592dc63e117d8f5af5f32a10d7e0651832d2/patch/int3472-support-independent-clock-and-LED-gpios-5.17+.patch. [Test Case] Tested on both TGL/ADL platforms against nominated kernels. [Where problems could occur] This adds exceptional cases with fallbacks to the original function. No one else is affected. [Other Info] This is an essential part for switching from power_ctrl_logic based GPIO control mechanism to the generic, upstreamed int3472 driver. Affects all IPU6 platforms that are to run new IPU6 driver dump in 202208. == original bug report == Per https://github.com/intel/ipu6-drivers/commit/f771bd3cb9f324a393a75e068a039bd1f9611026 and https://github.com/intel/ipu6-drivers/commit/2b8a592dc63e117d8f5af5f32a10d7e0651832d2, additional fix for INT3472 is necessary to probe camera sensor GPIOs on Intel IPU6 platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989647] Re: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux-oem-5.17 (Ubuntu) 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/1989647 Title: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] There's possibility that system will hang and no video output of two external monitor with dGPU W6400 Monitor 1: ASUS ProArt PA238Q (FHD) Monitor 2: Dell P2415Q (4K) [Fix] Introduce the dmi quirk in amdgpu, and add dmi quirks to bypass the affected machine. [Test Case] Two ways to verify Method 1: 1. Cold boot with ASUS 2. Attach Dell monitor. ASUS is primary. 3. Switch display mode to single ASUS 4. Switch disaply mode back to Joing Displays. ASUS is primary Method 2: 1. Cold boot with two monitors. ASUS is primary 2. Unplug the DP cable of Dell monitor from DUT and wait for few seconds 3. Plug it back to DUT [Where problems could occur] Low, add a dmi quirk to bypass the target machine. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988584] Re: cgroup: all controllers mounted when using 'cgroup_no_v1='
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: Confirmed => 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/1988584 Title: cgroup: all controllers mounted when using 'cgroup_no_v1=' Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: [Impact] When mounting a cgroup hierarchy with disabled controller in cgroup v1, all available controllers will be attached. For example, boot with cgroup_no_v1=cpu or cgroup_disable=cpu, and then mount with "mount -t cgroup -ocpu cpu /sys/fs/cgroup/cpu", then all enabled controllers will be attached except cpu. This exists since linux v5.1 and fixed in linux v5.11 with this commit: 61e960b07b63 cgroup-v1: add disabled controller check in cgroup1_parse_param() https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61e960b07b637 [Test Case] root@dut-vm:~# kexec -l /boot/vmlinuz-5.4.0-122-generic --initrd=/boot/initrd.img-5.4.0-122-generic --command-line="$(cat /proc/cmdline) cgroup_no_v1=net_prio,net_cls" root@dut-vm:~# systemctl kexec root@dut-vm:~# mount | grep cgroup tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,cpu,cpuacct,blkio,memory,devices,freezer,perf_event,hugetlb,pids,rdma) => All controllers are associated to /sys/fs/cgroup/net_cls,net_prio. Note that several reboots may be needed to reproduce the problem (it fails only when systemd tries to mount 'net_cls,net_prio' first, but the order is random). [Regression Potential] The patch is located in cgroup1_parse_param(), the potential regressions are low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988584/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989647] Re: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
** No longer affects: linux-oem-5.14 (Ubuntu Focal) ** No longer affects: linux-oem-5.14 (Ubuntu Jammy) ** No longer affects: linux-oem-5.14 (Ubuntu) ** No longer affects: linux-oem-5.17 (Ubuntu Focal) ** No longer affects: linux (Ubuntu Focal) ** Tags added: oem-priority originate-from-1971222 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989647 Title: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] There's possibility that system will hang and no video output of two external monitor with dGPU W6400 Monitor 1: ASUS ProArt PA238Q (FHD) Monitor 2: Dell P2415Q (4K) [Fix] Introduce the dmi quirk in amdgpu, and add dmi quirks to bypass the affected machine. [Test Case] Two ways to verify Method 1: 1. Cold boot with ASUS 2. Attach Dell monitor. ASUS is primary. 3. Switch display mode to single ASUS 4. Switch disaply mode back to Joing Displays. ASUS is primary Method 2: 1. Cold boot with two monitors. ASUS is primary 2. Unplug the DP cable of Dell monitor from DUT and wait for few seconds 3. Plug it back to DUT [Where problems could occur] Low, add a dmi quirk to bypass the target machine. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988809] Re: ip/nexthop: fix default address selection for connected nexthop
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988809
Title:
ip/nexthop: fix default address selection for connected nexthop
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
In Progress
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
Packets sent by userland apps are rejected/dropped if the source
address is not specified and the corresponding route is using a
connected nexthop object.
This bug exists since linux v5.3 and has been fixed in v5.19 by the following
upstream commits:
- 747c14307214 ("ip: fix dflt addr selection for connected nexthop")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=747c14307214
- cd72e61bad14 ("selftests/net: test nexthop without gw")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cd72e61bad14
- eb55dc09b5dd ("ip: fix triggering of 'icmp redirect'")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb55dc09b5dd
The last commit (v6.0) fixes a regression introduced by the first
commit.
[Test Case]
A detailed test case is explained in the first commit and a self-test
is added in the second commit.
[Regression Potential]
The patch modifies some internal routing states. It has been living in the
upstream trees for 2 months and the reported regression about icmp redirects
has been fixed.
The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988809/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] 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 1989649 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/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: Incomplete Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989578] Re: Add HDMI codec ID for Intel Raptor Lake
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1989578 Title: Add HDMI codec ID for Intel Raptor Lake Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [SRU Justification] [Impact] The HDAudio is not functional on some RaptorLake machines. The audio codec is failed to be probed so no PCM stream available for audio functions. [Fix] Backport the patch from upstream which adds the support for the HDMI codec ID on RaptorLake. [Test] Power on the machine and check if the audio function's working with alsa utilities. [Where problems could occur] The change only applies to the new RaptorLake Intel HDA controller and HDMI codec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989647] Re: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400)
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989647 Title: Fix AMDGPU: No video output and system hangs with two monitor (dGPU: W6400) Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: New Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] There's possibility that system will hang and no video output of two external monitor with dGPU W6400 Monitor 1: ASUS ProArt PA238Q (FHD) Monitor 2: Dell P2415Q (4K) [Fix] Introduce the dmi quirk in amdgpu, and add dmi quirks to bypass the affected machine. [Test Case] Two ways to verify Method 1: 1. Cold boot with ASUS 2. Attach Dell monitor. ASUS is primary. 3. Switch display mode to single ASUS 4. Switch disaply mode back to Joing Displays. ASUS is primary Method 2: 1. Cold boot with two monitors. ASUS is primary 2. Unplug the DP cable of Dell monitor from DUT and wait for few seconds 3. Plug it back to DUT [Where problems could occur] Low, add a dmi quirk to bypass the target machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] Re: [Hyper-V] Login screen does not appear
P.S. I have never tried hyperv_drm - I guess it should give VMs Wayland support? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: New Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989649] Re: [Hyper-V] Login screen does not appear
> I forgot to mention that plymouth failed to start as well Yes plymouth would fail to start for the same reason why there was no login screen -- non-working kernel graphics devices. But I really can't see what's gone wrong here. The correct kernel modules are reported as loaded already. It looks like hyperv_drm was failing to work at all, and hyperv_fb was working but the gdm user lacked permission to access it. ** Changed in: linux (Ubuntu) Importance: Critical => Undecided ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1989649 Title: [Hyper-V] Login screen does not appear Status in linux package in Ubuntu: New Bug description: Below are the packages were updated. After reboot, the GDM login screen did not appear. Start-Date: 2022-09-14 15:57:04 Commandline: packagekit role='update-packages' Upgrade: python3-distupgrade:amd64 (1:22.04.13, 1:22.04.14), gnome-control-center-faces:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), xserver-xorg-video-amdgpu:amd64 (22.0.0-1build1, 22.0.0-1ubuntu0.1), ubuntu-release-upgrader-gtk:amd64 (1:22.04.13, 1:22.04.14), gir1.2-javascriptcoregtk-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), gnome-control-center-data:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), gnome-control-center:amd64 (1:41.7-0ubuntu0.22.04.1, 1:41.7-0ubuntu0.22.04.5), libwebkit2gtk-4.0-37:amd64 (2.36.6-0ubuntu0.22.04.1, 2.36.7-0ubuntu0.22.04.1), ubuntu-release-upgrader-core:amd64 (1:22.04.13, 1:22.04.14), intel-microcode:amd64 (3.20220510.0ubuntu0.22.04.1, 3.20220809.0ubuntu0.22.04.1) End-Date: 2022-09-14 15:57:25 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 14 21:49:27 2022 InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989649/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934479] Re: chacha.bidir in tls from ubuntu_kernel_selftests net failed on F-oem-5.13
** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1934479 Title: chacha.bidir in tls from ubuntu_kernel_selftests net failed on F-oem-5.13 Status in ubuntu-kernel-tests: Fix Released Status in linux-oem-5.13 package in Ubuntu: Fix Released Bug description: Issue found on 5.13.0-1005.5 with node vought Test failed with: # # FAIL tls.12_chacha.bidir # # FAIL tls.13_chacha.bidir # # FAILED: 177 / 179 tests passed. Please find attachment for complete test output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1934479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
