[Kernel-packages] [Bug 1950778] Re: Ubuntu 20.04.3 generates IO error message during FIO stress.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950778 Title: Ubuntu 20.04.3 generates IO error message during FIO stress. Status in linux package in Ubuntu: Expired Bug description: With fio stress on Powerstore fcoe drives (lun) attached by using Qlogic QL41000 series controller, ubuntu 20.04.3 on MX740c blade server generates below mentioned i/o errors. Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1523]:13: Error detection CQE, xid=0x7bd Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1525]:13: err_warn_bitmap=0040: Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1529]:13: tx_buff_off=, rx_buff_off=, rx_id=041b Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1523]:3: Error detection CQE, xid=0x34d Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1525]:3: err_warn_bitmap=0040: Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1529]:3: tx_buff_off=, rx_buff_off=, rx_id=01f7 Steps to reproduce. 1. Configure QL41000 series controller on MX MX740c blade server. 2. Configure APM3246 array directly connected to chassis module MX9116n. 3. Install Ubuntu 20.04.3 in any local drive. 4. start I/O by using fio : # fio FileSystemCreateSingle/fio_test.cfg then we can observe error message in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968255] Re: Sudden, unexpected restart of the whole system. Reporting after automatic restart
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1968255 Title: Sudden, unexpected restart of the whole system. Reporting after automatic restart Status in linux package in Ubuntu: Expired Bug description: Using browser the system just stopped and restarted. Browser hardware acceleration option was on. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 8 07:25:13 2022 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-02 (1344 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969482] Re: zfs-2.1.4+ sru
I can also confirm that the fixes in -proposed fixes some severe performance issues on my system, with an encrypted ZFS root filesystem. It should be noted that if you're using ZFS on an Intel machine with < 4 physical cores, these performance regressions are severe enough to cause the entire machine to noticeably stutter and freeze when the disk is accessed - so this is a fairly serious performance regression for a lot of laptop users! I think the reason why it's so severe on this configuration is due to ZFS read/write spawning 4 tasks, which have a niceness of -20 causing the userspace to be starved (and perhaps security mitigations stopping/hindering the userspace from using hyperthreading). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969482 Title: zfs-2.1.4+ sru Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: Fix Committed Bug description: [Impact] * Upstream stable point release update with bugfixes, performance fixes, and newer kernel support as needed already in the OEM kernel and will be needed in the future HWE kernels. [Test Plan] * autopkgtest pass * kernel regression zfs testsuite pass * zsys integration test pass [Where problems could occur] * The stable branches maintain api/abi. Certain bugfixes do change userspace visible behavior of either succeeeding (when previously operations failed), or return errors when previously succeeding in error. For example there are changes when unlinking files in full volumes; changes to fallocate behaviour, etc. Overall they are minor corner cases, and bugfixes to correct the bahaviour to what is universally expected and how things behave on other filesystems (i.e. ext4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978359] 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/1978359 Title: boot kernel errors Status in linux package in Ubuntu: Confirmed Bug description: Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: fbcon: Taking over console Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) This happens while booting a newer kernel than the gm kernel (-25) bug is reported here and a fix already posted https://github.com/intel/linux-intel-lts/issues/22 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alorenz1772 F pulseaudio /dev/snd/pcmC0D0p: alorenz1772 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 23:45:45 2022 InstallationDate: Installed on 2022-06-06 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release
[Kernel-packages] [Bug 1978359] [NEW] boot kernel errors
Public bug reported: Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: fbcon: Taking over console Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Jun 10 23:34:40 luke kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_PR.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Local Variables are initialized for Method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: No Arguments are initialized for method [_CPC] Jun 10 23:34:40 luke kernel: Jun 10 23:34:40 luke kernel: ACPI Error: Aborting method \_PR.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) This happens while booting a newer kernel than the gm kernel (-25) bug is reported here and a fix already posted https://github.com/intel/linux-intel-lts/issues/22 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alorenz1772 F pulseaudio /dev/snd/pcmC0D0p: alorenz1772 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 23:45:45 2022 InstallationDate: Installed on 2022-06-06 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. Integrated Webcam HD Bus 001 Device 002: ID 275d:0ba6 USB OPTICAL MOUSE Bus 001 Device 005: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5490 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-37-generic
[Kernel-packages] [Bug 1978347] 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/1978347 Title: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27 Status in linux package in Ubuntu: Confirmed Bug description: IO on encrypted zfs root has fallen off a cliff in kernel versions after 5.15.0-27 (the degradation is observed since version 5.15.0-30, also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage almost hangs a new laptop (building large singularity images or synthetic testing with dd). I have confirmed that things are working as expected on a default + upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe SSD on the same laptop. There seems to be a regression when using the native zfs encryption (did aes-ni acceleration get turned off?) How to reproduce: - install ubuntu 22.04 desktop from iso, don't install web updates, check use zfs and encryption - sudo apt update && apt install dstat htop - create a dataset with compression disabled so that dd actually writes things to disk * sudo zfs create rpool/dummy * sudo zfs set compress=off rpool/dummy * sudo chown -R myusername. /dummy - start dstat and htop in the background (show kernel threads in the htop config) - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384 - sudo apt upgradeand reboot on the latest kernel, repeat Expected: some cpu load, dstat reports write speeds about as much as the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a 16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained for whatever WD 512GiB model I had laying around). Observed on versions -30 and later: 700% or more system cpu load, mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the system becomes somewhat unresponsive. Reads are also not good but I have not benchmarked. Booting the system and launching apps seems about normal due to the low IO load. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laperlej 4100 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 15:52:12 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-05-10 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2022 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.08.00 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.37.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.55 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4V1S3UP#ABL dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978347] [NEW] horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27
Public bug reported: IO on encrypted zfs root has fallen off a cliff in kernel versions after 5.15.0-27 (the degradation is observed since version 5.15.0-30, also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage almost hangs a new laptop (building large singularity images or synthetic testing with dd). I have confirmed that things are working as expected on a default + upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe SSD on the same laptop. There seems to be a regression when using the native zfs encryption (did aes-ni acceleration get turned off?) How to reproduce: - install ubuntu 22.04 desktop from iso, don't install web updates, check use zfs and encryption - sudo apt update && apt install dstat htop - create a dataset with compression disabled so that dd actually writes things to disk * sudo zfs create rpool/dummy * sudo zfs set compress=off rpool/dummy * sudo chown -R myusername. /dummy - start dstat and htop in the background (show kernel threads in the htop config) - dd if=/dev/zero of=/dummy/bigfile bs=1M count=16384 - sudo apt upgradeand reboot on the latest kernel, repeat Expected: some cpu load, dstat reports write speeds about as much as the SSD can sustain (2.9-3GiB/s with a 2TiB Samsung 970 EVO Plus for a 16GiB write test, 1.4GiB/s for a few seconds then 800MiB/s sustained for whatever WD 512GiB model I had laying around). Observed on versions -30 and later: 700% or more system cpu load, mostly in z_wr_iss threads, writes top at around 150-180MiB/s, the system becomes somewhat unresponsive. Reads are also not good but I have not benchmarked. Booting the system and launching apps seems about normal due to the low IO load. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laperlej 4100 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 15:52:12 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-05-10 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP EliteBook 850 G8 Notebook PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_rgwvzq@/vmlinuz-5.15.0-37-generic root=ZFS=rpool/ROOT/ubuntu_rgwvzq ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2022 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: T76 Ver. 01.08.00 dmi.board.name: 8846 dmi.board.vendor: HP dmi.board.version: KBC Version 30.37.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 48.55 dmi.modalias: dmi:bvnHP:bvrT76Ver.01.08.00:bd01/11/2022:br8.0:efr48.55:svnHP:pnHPEliteBook850G8NotebookPC:pvr:rvnHP:rn8846:rvrKBCVersion30.37.00:cvnHP:ct10:cvr:sku4V1S3UP#ABL: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G8 Notebook PC dmi.product.sku: 4V1S3UP#ABL dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "dmesg-outputs.tar.gz" https://bugs.launchpad.net/bugs/1978347/+attachment/5596539/+files/dmesg-outputs.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978347 Title: horrible IO degradation with encrypted zfs root on kernels past 5.15.0-27 Status in linux package in Ubuntu: Confirmed Bug description: IO on encrypted zfs root has fallen off a cliff in kernel versions after 5.15.0-27 (the degradation is observed since version 5.15.0-30, also seen on -33 and -37, -25 and -27 work like a charm). Heavy usage almost hangs a new laptop (building large singularity images or synthetic testing with dd). I have confirmed that things are working as expected on a default + upgraded Ubuntu 22.04 desktop LVM+LUKS installation using another NVMe SSD on the same laptop. There seems to be a regression when using the native zfs encryption (did aes-ni acceleration get turned off?) How to reproduce: - install ubuntu 22.04 desktop from iso, don't install web updates, check use zfs and encryption - sudo apt update && apt install dstat htop - create a dataset with compression disabled so that dd actually writes things to disk * sudo zfs create rpool/dummy * sudo zfs set compress=off rpool/dummy * sudo chown -R
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
I can confirm that 5.18.13 kernel has no flickers and no GRUB workaround is needed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU 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/1958191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
** Changed in: linux (Ubuntu) Status: Expired => 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/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Status in linux package in Ubuntu: Confirmed Bug description: Request to include below mpt3sas driver bug fix patches in Ubuntu 22.04 kernel. These patches got accepted by the upstream and please find the corresponding commit IDs as below, 5db207d66d mpt3sas: Fix incorrect 4gb boundary check ca23ac823c mpt3sas: Remove scsi_dma_map errors messages 9211faa39a scsi: mpt3sas: Update persistent trigger pages from sysfs interface Below is the summary of each of the above bug fix commits, 1. mpt3sas: Fix incorrect 4gb boundary check: Without this patch, driver was checking whether any of it's pool crosses the 4gb boundary or not using the pool's virtual address instead of using it's dma address. So some time driver may false positively assume that the pool as crossed the 4gb boundary region (as it observes that pool's virtual address is crossing the 4gb boundary) even though it is really not. 2. mpt3sas: Remove scsi_dma_map errors messages: When driver set the DMA mask to 32bit then we observe that the SWIOTLB bounce buffers are getting exhausted quickly. For most of the IOs driver observe that scsi_dma_map() API returned with failure status and hence driver was printing below error message. Since this error message is getting printed per IO and if user issues heavy IOs then we observe that kernel overwhelmed with this error message. Also we will observe the kernel panic when the serial console is enabled. So to limit this issue, we removed this error message though this patch. "scsi_dma_map failed: request for 1310720 bytes!" 3. mpt3sas: Update persistent trigger pages from sysfs interface: When user set's any diag buffer trigger conditions then driver has to save these trigger conditions in the controller Firmware's NVRAM region. So that when system reboots then driver can get these trigger conditions from Firmware's NVRAM region and set these trigger conditions automatically. so that user no need to set these conditions again. Without this patch driver was not not saving these user provided trigger conditions in the Firmware's NVRAM region. Please let me if I have missed to add any data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978333] [NEW] Remove "ata_piix.prefer_ms_hyperv=0" parameter
Public bug reported: Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" parameter. target series - Kinetic-> Bionic upstream patch https://salsa.debian.org/debian/kdump- tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503 Thanks! ** Affects: kdump-tools (Ubuntu) Importance: Undecided Assignee: Heather Lemon (hypothetical-lemon) Status: New ** Affects: kdump-tools (Ubuntu Bionic) Importance: Undecided Assignee: Heather Lemon (hypothetical-lemon) Status: New ** Affects: kdump-tools (Ubuntu Focal) Importance: Undecided Assignee: Heather Lemon (hypothetical-lemon) Status: New ** Affects: kdump-tools (Ubuntu Jammy) Importance: Undecided Assignee: Heather Lemon (hypothetical-lemon) Status: New ** Affects: kdump-tools (Ubuntu Kinetic) Importance: Undecided Assignee: Heather Lemon (hypothetical-lemon) Status: New ** Also affects: kdump-tools (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: kdump-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: kdump-tools (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: kdump-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: kdump-tools (Ubuntu Bionic) Assignee: (unassigned) => Heather Lemon (hypothetical-lemon) ** Changed in: kdump-tools (Ubuntu Focal) Assignee: (unassigned) => Heather Lemon (hypothetical-lemon) ** Changed in: kdump-tools (Ubuntu Jammy) Assignee: (unassigned) => Heather Lemon (hypothetical-lemon) ** Changed in: kdump-tools (Ubuntu Kinetic) Assignee: (unassigned) => Heather Lemon (hypothetical-lemon) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: New Status in kdump-tools source package in Bionic: New Status in kdump-tools source package in Focal: New Status in kdump-tools source package in Jammy: New Status in kdump-tools source package in Kinetic: New Bug description: Back-porting a fix from upstream to remove "ata_piix.prefer_ms_hyperv=0" parameter. target series - Kinetic-> Bionic upstream patch https://salsa.debian.org/debian/kdump- tools/-/commit/b1bac9396ddbbce3817c34be3161630698e4a503 Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1978333/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969482] Re: zfs-2.1.4+ sru
I tested this version and it does fix a (severe) performance regression as mentioned here (#1977699) https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1977699. Would this be released before 21.10 reaches EOL? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969482 Title: zfs-2.1.4+ sru Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: Fix Committed Bug description: [Impact] * Upstream stable point release update with bugfixes, performance fixes, and newer kernel support as needed already in the OEM kernel and will be needed in the future HWE kernels. [Test Plan] * autopkgtest pass * kernel regression zfs testsuite pass * zsys integration test pass [Where problems could occur] * The stable branches maintain api/abi. Certain bugfixes do change userspace visible behavior of either succeeeding (when previously operations failed), or return errors when previously succeeding in error. For example there are changes when unlinking files in full volumes; changes to fallocate behaviour, etc. Overall they are minor corner cases, and bugfixes to correct the bahaviour to what is universally expected and how things behave on other filesystems (i.e. ext4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949770] Re: Enable arm64 for Hyper-V guests
** Changed in: linux-meta-azure (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-meta-azure (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: linux-signed-azure (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-signed-azure (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: linux-azure (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-azure (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1949770 Title: Enable arm64 for Hyper-V guests Status in linux-azure package in Ubuntu: Fix Released Status in linux-meta-azure package in Ubuntu: Fix Released Status in linux-signed-azure package in Ubuntu: Fix Released Status in linux-azure source package in Hirsute: Fix Released Status in linux-meta-azure source package in Hirsute: Fix Released Status in linux-signed-azure source package in Hirsute: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-meta-azure source package in Impish: Fix Released Status in linux-signed-azure source package in Impish: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-meta-azure source package in Jammy: Fix Released Status in linux-signed-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Since linux-azure can also be used for local Hyper-V guests on Windows 10 Pro running on arm64 platforms, enable arm64 build for this kernel as well. [Test Case] Boot an arm64 VM on a machine running Win10Pro with Hyper-V. [Where things could go wrong] Some of the patches touch common PCI code. Device detection could be impacted. [Other info] SF: #00310705 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1949770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946744] Re: linux-azure: cifs: use the expiry output of dns_query to schedule next resolution
*** This bug is a duplicate of bug 1960549 *** https://bugs.launchpad.net/bugs/1960549 ** This bug has been marked a duplicate of bug 1960549 Azure: CIFS backport request -- 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/1946744 Title: linux-azure: cifs: use the expiry output of dns_query to schedule next resolution Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] We recently fixed DNS resolution of the server hostname during reconnect. However, server IP address may change, even when the old one continues to server (although sub-optimally). We should schedule the next DNS resolution based on the TTL of the DNS record used for the last resolution. This way, we resolve the server hostname again when a DNS record expires. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=506c1da44fee32ba1d3a70413289ad58c772bba6 [Test Case] Microsoft tested [Regression potential] Samba Reconnects may fail. [Other Info] SF: #00320698 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1946744/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961329] Re: linux-azure: Update HV support to 5.17
** Changed in: linux-azure (Ubuntu Focal) Status: New => Won't Fix -- 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/1961329 Title: linux-azure: Update HV support to 5.17 Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Won't Fix Status in linux-azure source package in Impish: Fix Released Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Microsoft has requested these commits be present in all Azure tuned kernels: ac0f7d42584125dab8039e60ab4ade48cc2db61c Drivers: hv: copy from message page only what's needed a276463b7aeb6186e7e4315cccb032773fb31b5d Drivers: hv: allocate the exact needed memory for messages 5cc415001bca8fe0e3f0ee6d58a953a314dd9751 Drivers: hv: avoid passing opaque pointer to vmbus_onmessage() b0a284dc65b401a508dc2c5ed7d465884220f607 Drivers: hv: make sure that 'struct vmbus_channel_message_header' compiles correctly 52c7803f9bd4b1f0ac6e2e3e6051415198cc06bd Drivers: hv: check VMBus messages lengths 06caa778d8b2fbcb4ac3878751e39d116424ba9b hv_utils: Add validation for untrusted Hyper-V values e99c4afbee07e9323e9191a20b24d74dbf815bdf Drivers: hv: vmbus: Initialize memory to be sent to the host fe8c1b18a27de4d6ca5d99b3ffb3125dc69a5b76 Drivers: hv: vmbus: Copy the hv_message in vmbus_on_msg_dpc() e3fa4b747f085d2cda09bba0533b86fa76038635 Drivers: hv: vmbus: Avoid use-after-free in vmbus_onoffer_rescind() e4d221b42354b2e2ddb9187a806afb651eee2cda Drivers: hv: vmbus: Resolve race condition in vmbus_onoffer_rescind() adae1e931acd8b430d31141a283ea06d4b705417 Drivers: hv: vmbus: Copy packets sent by Hyper-V out of the ring buffer 9d68cd9120e4e3af38f843e165631c323b86b4e4 hv_utils: Set the maximum packet size for VSS driver to the length of the receive buffer f1940d4e9cbe6208e7e77e433c587af108152a17 Drivers: hv: vmbus: Fix kernel crash upon unbinding a device from uio_hv_generic driver 007faec014cb5d26983c1f86fd08c6539b41392e x86/sev: Expose sev_es_ghcb_hv_call() for use by HyperV 0cc4f6d9f0b9f20f3f1e1149bdb6737c0b4e134a x86/hyperv: Initialize GHCB page in Isolation VM af788f355e343373490b7d2e361016e7c24a0ffa x86/hyperv: Initialize shared memory boundary in the Isolation VM. 810a521265023a1d5c6c081ea2d216bc63d422f5 x86/hyperv: Add new hvcall guest address host visibility support d4dccf353db80e209f262e3973c834e6e48ba9a9 Drivers: hv: vmbus: Mark vmbus ring buffer visible to host in Isolation VM faff44069ff538ccdfef187c4d7ec83d22dfb3a4 x86/hyperv: Add Write/Read MSR registers via ghcb page 20c89a559e00dfe352b73e867211a669113ae881 x86/hyperv: Add ghcb hvcall support for SNP VM f2f136c05fb6093818a3b3fefcba46231ac66a62 Drivers: hv: vmbus: Add SNP support for VMbus channel initiate message 9a8797722e4239242d0cb4cc4baa805df6ac979e Drivers: hv: vmbus: Initialize VMbus ring buffer for Isolation VM 1a5e91d8375fc8369207cc0b9894a324f2bbf1d9 swiotlb: Add swiotlb bounce buffer remap function for HV IVM c789b90a69045d1924bc0802ae0dce2bba05a04e x86/hyper-v: Add hyperv Isolation VM check in the cc_platform_has() 062a5c4260cdb734a4727230c58e38accf413315 hyper-v: Enable swiotlb bounce buffer for Isolation VM 743b237c3a7b0f5b44aa704aae8a1058877b6322 scsi: storvsc: Add Isolation VM support for storvsc driver 846da38de0e8224f2f94b885125cf1fd2d7b0d39 net: netvsc: Add Isolation VM support for netvsc driver 2deb55d9f57bb7a877c0d77115cc4077e1e974ff swiotlb: Add CONFIG_HAS_IOMEM check around swiotlb_mem_remap() 6a27e396ebb149fc47baccc1957a7a9dd70049a7 Drivers: hv: vmbus: Initialize request offers message for Isolation VM 4eea5332d67d8ae6ba5717ec0f4e671fdbd222e7 scsi: storvsc: Fix storvsc_queuecommand() memory leak 96d9d1fa5cd505078534113308ced0aa56d8da58 Drivers: hv: balloon: account for vmbus packet header in max_pkt_size [Test Plan] Microsoft tested [Where things could go wrong] Hyper-V guests may not work correctly. [Other Info] SF: #00323683 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1961329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973254] 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 1973254 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/1973254 Title: uc22 pc-kernel 5.15.0-30.31.1 iwlwifi Hardware error detected. Restarting. Status in linux package in Ubuntu: Incomplete Status in snapd package in Ubuntu: New Bug description: None of our wifi tests seem to be working on one of the amd64 systems we use for testing full disk encryption. The current kernel snap installed is: pc-kernel 5.15.0-30.31.1 99122/betacanonical✓ kernel When looking through the dmesg output, I found a call trace related to iwlwifi which repeats a lot of times. I've attached a section of it as dmesg.txt, as well as dmesg output from right after a fresh boot (dmesg-boot.txt) so you can see the earlier messages, firmware loading, etc. The relevant firmware line from dmesg is: [ 13.667426] iwlwifi :00:14.3: loaded firmware version 66.f1c864e0.0 QuZ-a0-jf-b0-66.ucode op_mode iwlmvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962610] Re: linux-azure: prevent VMbus deadlock
** Changed in: linux-azure (Ubuntu)
Status: New => Won't Fix
--
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/1962610
Title:
linux-azure: prevent VMbus deadlock
Status in linux-azure package in Ubuntu:
Won't Fix
Bug description:
SRU Justification
[Impact]
The kernel can deadlock
[Fix]
240ad77cb50d9f0a961fcb0f21e67939cf7a9c04 ("PCI: hv: Prepare
hv_compose_msi_msg() for the VMBus-channel-interrupt-to-vCPU
reassignment functionality")
[Test Plan]
Microsoft tested
[Other Info]
SF: #00329336
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1962610/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973254] Re: uc22 pc-kernel 5.15.0-30.31.1 iwlwifi Hardware error detected. Restarting.
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973254 Title: uc22 pc-kernel 5.15.0-30.31.1 iwlwifi Hardware error detected. Restarting. Status in linux package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: None of our wifi tests seem to be working on one of the amd64 systems we use for testing full disk encryption. The current kernel snap installed is: pc-kernel 5.15.0-30.31.1 99122/betacanonical✓ kernel When looking through the dmesg output, I found a call trace related to iwlwifi which repeats a lot of times. I've attached a section of it as dmesg.txt, as well as dmesg output from right after a fresh boot (dmesg-boot.txt) so you can see the earlier messages, firmware loading, etc. The relevant firmware line from dmesg is: [ 13.667426] iwlwifi :00:14.3: loaded firmware version 66.f1c864e0.0 QuZ-a0-jf-b0-66.ucode op_mode iwlmvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
Fixed kernel works like a charm. @matthew-nocturnal you have to change the default GRUB that loads, so it is on /etc/default/grub. There you change the DEFAULT_GRUB with another one, as has been pointed out in the previous messages. But now you can simply run apt update / upgrade and it should get the latest kernel. If you can't access the machine to do this, you can either use a rescue machine, and do it with chroot, or try to disable docker before it crashes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963]
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
How did people fix this on aws instances that have no serial console access? assuming the disk was mounted and grub.cfg was edited. what did you change in the grub.cfg? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS:
[Kernel-packages] [Bug 1978145] Re: Request to back port vmci patches to Ubuntu kernel
Please try the test kernel at https://kernel.ubuntu.com/~rtg/jammy-vmci-
updates-lp1978145/5.15.0-37.38~lp1978145.1/
wget
https://kernel.ubuntu.com/~rtg/jammy-vmci-updates-lp1978145/5.15.0-37.38~lp1978145.1/amd64/linux-image-unsigned-5.15.0-37-generic_5.15.0-37.38~lp1978145.1_amd64.deb
wget
https://kernel.ubuntu.com/~rtg/jammy-vmci-updates-lp1978145/5.15.0-37.38~lp1978145.1/amd64/linux-modules-5.15.0-37-generic_5.15.0-37.38~lp1978145.1_amd64.deb
sudo dpkg -i *.deb
sudo reboot
You can view the kernel sources at 'git://git.launchpad.net/~timg-
tpi/ubuntu/+source/linux/+git/jammy jammy-vmci-updates-lp1978145'
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1978145
Title:
Request to back port vmci patches to Ubuntu kernel
Status in linux package in Ubuntu:
Confirmed
Bug description:
The request is to bring vmci to TOT and back port the following patches into
Ubuntu kernels.
1. fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace
formatting change for vmci register defines")
2. e283a0e8b7ea83915e988ed059384af166b444c0 ("VMCI: dma dg: add MMIO access
to registers")
3. eed2298d936087a1c85e0fa6f7170028e4f4fded ("VMCI: dma dg: detect DMA
datagram capability")
4. 8cb520bea1470ca205980fbf030ed1f472f4af2f ("VMCI: dma dg: set OS page
size")
5. cc68f2177fcbfe2dbe5e9514789b96ba5995ec1e ("VMCI: dma dg: register dummy
IRQ handlers for DMA datagrams")
6. 5ee109828e73bbe4213c373988608d8f33e03d78 ("VMCI: dma dg: allocate send
and receive buffers for DMA datagrams")
7. 22aa5c7f323022477b70e044eb00e6bfea9498e8 ("VMCI: dma dg: add support for
DMA datagrams sends")
8. 463713eb6164b6577f8e91447c7745628215531b ("VMCI: dma dg: add support for
DMA datagrams receive")
9. 77e861619baea5a7c934e47fda74b03c0b072aec ("VMCI: Fix some error handling
paths in vmci_guest_probe_device()")
10. c8e9b30ccae605bf1dbeaf03971f9b83f70b928d ("VMCI: Release
notification_bitmap in error path")
11. 5df0e734b8c39598effe0f17e5bd8ff7748a0693 ("VMCI: Check exclusive_vectors
when freeing interrupt 1")
12. 1f7142915d304804a9bd952245fce92786b1b62f ("VMCI: Add support for ARM64")
13. ba03a9bbd17b149c373c0ea44017f35fc2cd0f28 ("VMCI: Release resource if the
work is already queued")
Thanks,
Vishnu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978145/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971460] Re: [amdgpu] System freezes coming out from suspension or randomly from screen power save
After 2 kernel update now the situation using Wayland is better with my RX 6600 expecially in returning from suspend. But there's still random freeze on power on of monitor after screen suspend and sync back 144hz. Still lot of errors on amdgpu module. Attach log file. ** Attachment added: "freeze_on_monitor_powersave_144hz.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971460/+attachment/5596450/+files/freeze_on_monitor_powersave_144hz.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/1971460 Title: [amdgpu] System freezes coming out from suspension or randomly from screen power save Status in linux package in Ubuntu: Confirmed Bug description: I've Ubuntu 22.04 with Wayland and Sapphire Radeon RX 6600 with Xiaomi 34" curved gaming monitor capable of 3440x1440 @144,00hz. Using refresh of 120hz or 144hz, the system freezes coming out from suspension or randomly from screen power save. Setting @60hz it's more stable. It seems something related to wrong Modeline for this VGA and monitor resolution/frequencies. The problem is with both DP or HDMI cable. With HDMI it supports only 99,99hz I had no problem with the provious HP RX 460 HanSolo or XFX GTX 1060 3GB with proprietary nVidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 3 18:29:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] [1002:73ff] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 23 [Radeon RX 6600/6600 XT/6600M] [1da2:e447] InstallationDate: Installed on 2022-04-23 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=be1c4139-f2bc-472b-87c1-099f2be97b1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: TUF B450M-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3604:bd02/25/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450M-PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975516] Re: System freeze
*** This bug is a duplicate of bug 1978133 *** https://bugs.launchpad.net/bugs/1978133 ** This bug has been marked a duplicate of bug 1978133 System freeze followed by kernel panic or blank screen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975516 Title: System freeze Status in linux package in Ubuntu: Confirmed Bug description: I had LibreOffice Writer open at the time, but it was idle. The system became completely unresponsive and a power reset was the only way to shut it down. The "REISUB" command didn't work. I had Ubuntu 21.10 and Debian 11 before, and this was not reproducible with them. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dsilva 1511 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 23 13:48:05 2022 InstallationDate: Installed on 2022-05-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic root=UUID=15cac922-78d2-4c88-aa40-a49c2bfda033 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0DC2CG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd04/21/2021:br1.13:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DC2CG:rvrA00:cvnDellInc.:ct10:cvr:sku08CA: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
All of the updated 5.13 kernels have now made it to the archive and into both the focal-updates and focal-security pockets. That list of kernels is: linux-aws-5.13 - 5.13.0-1029.32~20.04.1 linux-azure-5.13 - 5.13.0-1029.34~20.04.1 linux-gcp-5.13 - 5.13.0-1031.37~20.04.1 linux-oracle-5.13 - 5.13.0-1034.40~20.04.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
In Oracle Cloud you can start a cloud shell console connection then force reboot the instance and in the console press esc, in the Grub menu select the previous kernel. I was able to boot with kernel 5.13.0-1030-oracle without panics. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5
[Kernel-packages] [Bug 1978317] [NEW] package linux-firmware 1.187.31 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: Standard update. This is another variation of numerous bug reports ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.31 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 2080 F pulseaudio /dev/snd/controlC0: chris 2080 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jun 10 14:17:18 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=3eb0cc8f-10d5-466f-ad48-7ad42d84e9b1 InstallationDate: Installed on 2015-12-07 (2377 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-117-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.31 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-06-22 (352 days ago) dmi.bios.date: 12/04/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88X-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd12/04/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88X-PRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1978317 Title: package linux-firmware 1.187.31 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: Standard update. This is another variation of numerous bug reports ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.31 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 2080 F pulseaudio /dev/snd/controlC0: chris 2080 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jun 10 14:17:18 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=3eb0cc8f-10d5-466f-ad48-7ad42d84e9b1 InstallationDate: Installed on 2015-12-07 (2377 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-117-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.31 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-06-22 (352 days ago) dmi.bios.date: 12/04/2014 dmi.bios.vendor:
[Kernel-packages] [Bug 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
The Intel Xeon Platinum 8380 is an IceLake chip (see https://www.intel.com/content/www/us/en/products/sku/212287/intel-xeon- platinum-8380-processor-60m-cache-2-30-ghz/specifications.html). The change referenced by Zhanglei only addresses chips that are Skylake-X. There is a change in the upstream kernel that changes how this SNC detection works to now default it on except for COD (Cluster-on-Die, SNC is a newer implementation of this tech it seems): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.19-rc1=2c88d45edbb89029c1190bb3b136d2602f057c98 The hwe-5.13 kernel has this change, but the 5.4 kernel does not. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here ] Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Apr 6 02:33:31 G292-280 kernel: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Code: 41 5c 5d c3 80 3d 1e 75 ba 01 00 75 ec 89 f1 41 89 d9 89 fe 45 89 e0 48 c7 c7 b8 00 b4 a6 c6 05 04 75 ba 01 01 e8 b4 c7 03 00 <0f> 0b eb cb 0f 1f 44 00 00 55 0f b6 05 a3 8d f0 01 c6 05 9c 8d f0 Apr 6 02:33:31 G292-280 kernel: [0.007531] RSP: :b76b58e17eb8 EFLAGS: 00010086 Apr 6 02:33:31 G292-280 kernel: [0.007531] RAX: RBX: RCX: a7264e88 Apr 6 02:33:31 G292-280 kernel: [0.007531] RDX: a7264e88 RSI: 0096 RDI: 0046 Apr 6 02:33:31 G292-280 kernel: [0.007531] RBP: b76b58e17ec8 R08: R09: 0002f680 Apr 6 02:33:31 G292-280 kernel: [0.007531] R10: 8b69bf80 R11: 02c0 R12: 0001 Apr 6 02:33:31 G292-280 kernel: [0.007531] R13: 0014 R14: 0014 R15: 0002 Apr 6 02:33:31 G292-280 kernel: [0.007531] FS: () GS:8b69bf80() knlGS: Apr 6 02:33:31 G292-280 kernel: [0.007531] CS: 0010 DS: ES: CR0: 80050033 Apr 6 02:33:31 G292-280 kernel: [0.007531] CR2: CR3: 007ee1a0a001 CR4: 00760ee0 Apr 6 02:33:31 G292-280 kernel: [0.007531] DR0: DR1: DR2: Apr 6 02:33:31 G292-280 kernel: [0.007531] DR3: DR6: fffe0ff0 DR7: 0400 Apr 6 02:33:31 G292-280 kernel: [0.007531] PKRU: Apr 6 02:33:31 G292-280 kernel: [0.007531] Call Trace: Apr 6 02:33:31 G292-280 kernel: [0.007531] set_cpu_sibling_map+0x14f/0x600 Apr 6 02:33:31 G292-280 kernel: [0.007531] start_secondary+0x6e/0x1c0 Apr 6 02:33:31 G292-280 kernel: [0.007531] secondary_startup_64+0xa4/0xb0 Apr 6 02:33:31 G292-280 kernel: [0.007531] ---[ end trace 789d1f3abd3d96d4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975582] Re: [UBUNTU 20.04] rcu stalls with many storage key guests
Added test builds for Impish and Jammy on top of the focal ones: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975582 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975582 Title: [UBUNTU 20.04] rcu stalls with many storage key guests Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: == [Impact] * Ubuntu on s390x KVM environments with lots of large guests with storage keys can be affected by rcu stalls. * These rcu stalls can cause the system to crash/dump. [Fix] * 3ae11dbcfac9 3ae11dbcfac906a8c3a480e98660a823130dc16a "s390/mm: use non-quiescing sske for KVM switch to keyed guest" * 6d5946274df1 6d5946274df1fff539a7eece458a43be733d1db8 "s390/gmap: voluntarily schedule during key setting" [Test Plan] * There is no trigger or direct test or re-creation of the problem situation possible, but... * and IBM z13 or LinuxONE (or never) LPAR is needed that runs Ubuntu Server 20.04 LTS or 18.04 LTS with HWE kernel and acts as KVM host with again several large guests running on top with storage groups. * Let such a system running for days under significant load and watch the logs for rcu issues. * Prior to the submission of this SRU patched test kernels for focal 5.4 and bionic hwe-5.4 were created and tested. They ran for days at a staging environemnt at IBM without further issues. * The modifications are all limited to s390x. * A test kernel was build (see below) that ran in a test environment at IBM under appropriate load for several days. [Where problems could occur] * Due to the change for the KVM switch to keyed guest from classic sske to non-quiescing sske the KVM behaviour might have changed and the storage keys harmed. * The now more generous scheduling while setting keys has an impact on the guest memory management and mapping which will lead to a different performance. * This, with the introduction of __s390_enable_skey_pmd and cond_resched, might increase the overhead in certain situations, but eventually improves the responsiveness over time, hence avoid rcu stalls. [Other Info] * Since the patches are upstream in 5.19-rc1, they will be included in the kernel that is planned for kinetic (5.19). * Hence this is an SRU to jammy, impish and focal. __ ---Problem Description--- There can be rcu stalls when running lots of large guests with storage keys: [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU [1377614.579845] rcu: 18-: (2099 ticks this GP) idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 [1377614.579895](t=2100 jiffies g=155867385 q=20879) [1377614.579898] Task dump for CPU 18: [1377614.579899] CPU 1/KVM R running task0 1030947 256019 0x0604 [1377614.579902] Call Trace: [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0) [1377614.579918] [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 [1377614.579919] [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 [1377614.579924] [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 [1377614.579926] [<001f1eceb26c>] update_process_times+0x3c/0x80 [1377614.579931] [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 [1377614.579932] [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 [1377614.579933] [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 [1377614.579935] [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 [1377614.579938] [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 [1377614.579942] [<001f1f4c6d08>] ext_int_handler+0x130/0x134 [1377614.579945] [<001f1ec0af10>] ptep_zap_key+0x40/0x60 Contact Information = cborn...@de.ibm.com ---uname output--- RELEASE: 5.4.0-90-generic VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021 == Comment: #1 - Christian Borntraeger - 2022-05-24 03:59:37 == This is a test patch that might address the rcu stalls. == Comment: #2 - Christian Borntraeger - 2022-05-24 04:00:22 == This is a 2nd patch that reduces the cost of key setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1975582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975582] Re: [UBUNTU 20.04] rcu stalls with many storage key guests
SRU request submitted to the Ubuntu kernel team mailing list for jammy, impish and focal: https://lists.ubuntu.com/archives/kernel-team/2022-June/thread.html#130934 Changing status to 'In Progress' for jammy, impish and focal. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975582 Title: [UBUNTU 20.04] rcu stalls with many storage key guests Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: == [Impact] * Ubuntu on s390x KVM environments with lots of large guests with storage keys can be affected by rcu stalls. * These rcu stalls can cause the system to crash/dump. [Fix] * 3ae11dbcfac9 3ae11dbcfac906a8c3a480e98660a823130dc16a "s390/mm: use non-quiescing sske for KVM switch to keyed guest" * 6d5946274df1 6d5946274df1fff539a7eece458a43be733d1db8 "s390/gmap: voluntarily schedule during key setting" [Test Plan] * There is no trigger or direct test or re-creation of the problem situation possible, but... * and IBM z13 or LinuxONE (or never) LPAR is needed that runs Ubuntu Server 20.04 LTS or 18.04 LTS with HWE kernel and acts as KVM host with again several large guests running on top with storage groups. * Let such a system running for days under significant load and watch the logs for rcu issues. * Prior to the submission of this SRU patched test kernels for focal 5.4 and bionic hwe-5.4 were created and tested. They ran for days at a staging environemnt at IBM without further issues. * The modifications are all limited to s390x. * A test kernel was build (see below) that ran in a test environment at IBM under appropriate load for several days. [Where problems could occur] * Due to the change for the KVM switch to keyed guest from classic sske to non-quiescing sske the KVM behaviour might have changed and the storage keys harmed. * The now more generous scheduling while setting keys has an impact on the guest memory management and mapping which will lead to a different performance. * This, with the introduction of __s390_enable_skey_pmd and cond_resched, might increase the overhead in certain situations, but eventually improves the responsiveness over time, hence avoid rcu stalls. [Other Info] * Since the patches are upstream in 5.19-rc1, they will be included in the kernel that is planned for kinetic (5.19). * Hence this is an SRU to jammy, impish and focal. __ ---Problem Description--- There can be rcu stalls when running lots of large guests with storage keys: [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU [1377614.579845] rcu: 18-: (2099 ticks this GP) idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 [1377614.579895](t=2100 jiffies g=155867385 q=20879) [1377614.579898] Task dump for CPU 18: [1377614.579899] CPU 1/KVM R running task0 1030947 256019 0x0604 [1377614.579902] Call Trace: [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0) [1377614.579918] [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 [1377614.579919] [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 [1377614.579924] [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 [1377614.579926] [<001f1eceb26c>] update_process_times+0x3c/0x80 [1377614.579931] [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 [1377614.579932] [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 [1377614.579933] [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 [1377614.579935] [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 [1377614.579938] [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 [1377614.579942] [<001f1f4c6d08>] ext_int_handler+0x130/0x134 [1377614.579945] [<001f1ec0af10>] ptep_zap_key+0x40/0x60 Contact Information = cborn...@de.ibm.com ---uname output--- RELEASE: 5.4.0-90-generic VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021 == Comment: #1 - Christian Borntraeger - 2022-05-24 03:59:37 == This is a test patch that might address the rcu stalls. == Comment: #2 - Christian Borntraeger - 2022-05-24 04:00:22 == This is a 2nd patch that reduces the cost of key setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1975582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975592] Re: Enable Nezha board
** Description changed: Enable Nezha board Apply relevant patches to linux-riscv-5.17 kernel to enable nezha kernel flavour. + + Backport patches from https://github.com/AlexGhiti/riscv- + linux/tree/int/alex/nezha_Ubuntu-unstable-5.17.0-8.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1975592 Title: Enable Nezha board Status in linux-riscv package in Ubuntu: New Bug description: Enable Nezha board Apply relevant patches to linux-riscv-5.17 kernel to enable nezha kernel flavour. Backport patches from https://github.com/AlexGhiti/riscv- linux/tree/int/alex/nezha_Ubuntu-unstable-5.17.0-8.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1975592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975582] Re: [UBUNTU 20.04] rcu stalls with many storage key guests
** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Description changed: + SRU Justification: + == + + [Impact] + + * Ubuntu on s390x KVM environments with lots of large guests with storage +keys can be affected by rcu stalls. + + * These rcu stalls can cause the system to crash/dump. + + [Fix] + + * 3ae11dbcfac9 3ae11dbcfac906a8c3a480e98660a823130dc16a "s390/mm: use + non-quiescing sske for KVM switch to keyed guest" + + * 6d5946274df1 6d5946274df1fff539a7eece458a43be733d1db8 "s390/gmap: + voluntarily schedule during key setting" + + [Test Plan] + + * There is no trigger or direct test or re-creation of the +problem situation possible, but... + + * and IBM z13 or LinuxONE (or never) LPAR is needed that +runs Ubuntu Server 20.04 LTS or 18.04 LTS with HWE kernel +and acts as KVM host with again several large guests running +on top with storage groups. + + * Let such a system running for days under significant load +and watch the logs for rcu issues. + + * Prior to the submission of this SRU patched test kernels +for focal 5.4 and bionic hwe-5.4 were created and tested. +They ran for days at a staging environemnt at IBM +without further issues. + + * The modifications are all limited to s390x. + + * A test kernel was build (see below) that ran in a test environment +at IBM under appropriate load for several days. + + [Where problems could occur] + + * Due to the change for the KVM switch to keyed guest +from classic sske to non-quiescing sske +the KVM behaviour might have changed and the storage keys harmed. + + * The now more generous scheduling while setting keys +has an impact on the guest memory management and mapping +which will lead to a different performance. + + * This, with the introduction of __s390_enable_skey_pmd and +cond_resched, might increase the overhead in certain situations, +but eventually improves the responsiveness over time, +hence avoid rcu stalls. + + [Other Info] + + * Since the patches are upstream in 5.19-rc1, +they will be included in the kernel that is planned for kinetic (5.19). + + * Hence this is an SRU to jammy, impish and focal. + + __ + ---Problem Description--- There can be rcu stalls when running lots of large guests with storage keys: [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU - [1377614.579845] rcu: 18-: (2099 ticks this GP) idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 + [1377614.579845] rcu: 18-: (2099 ticks this GP) idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 [1377614.579895](t=2100 jiffies g=155867385 q=20879) [1377614.579898] Task dump for CPU 18: [1377614.579899] CPU 1/KVM R running task0 1030947 256019 0x0604 [1377614.579902] Call Trace: [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0) - [1377614.579918] [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 - [1377614.579919] [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 - [1377614.579924] [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 - [1377614.579926] [<001f1eceb26c>] update_process_times+0x3c/0x80 - [1377614.579931] [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 - [1377614.579932] [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 - [1377614.579933] [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 - [1377614.579935] [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 - [1377614.579938] [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 - [1377614.579942] [<001f1f4c6d08>] ext_int_handler+0x130/0x134 - [1377614.579945] [<001f1ec0af10>] ptep_zap_key+0x40/0x60 + [1377614.579918] [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 + [1377614.579919] [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 + [1377614.579924] [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 + [1377614.579926] [<001f1eceb26c>] update_process_times+0x3c/0x80 + [1377614.579931] [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 + [1377614.579932] [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 + [1377614.579933] [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 + [1377614.579935] [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 + [1377614.579938] [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 + [1377614.579942] [<001f1f4c6d08>] ext_int_handler+0x130/0x134 + [1377614.579945] [<001f1ec0af10>] ptep_zap_key+0x40/0x60 - -
[Kernel-packages] [Bug 1978296] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596416/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596415/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596414/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596413/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0
[Kernel-packages] [Bug 1978296] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596418/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596419/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596417/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596407/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596412/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596411/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14:
[Kernel-packages] [Bug 1978296] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596410/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596406/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15: 7f6d61d7af40
[Kernel-packages] [Bug 1978296] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596409/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596408/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596402/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596404/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15: 7f6d61d7af40
[Kernel-packages] [Bug 1978296] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596403/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1978296/+attachment/5596405/+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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15:
[Kernel-packages] [Bug 1978296] Re: System hang with kernel general protection fault
apport information ** Tags added: apport-collected jammy ** Description changed: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15: 7f6d61d7af40 Modules linked in: uhid ccm rfcomm nvidia_uvm(PO) cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi intel_tcc_cooling snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_ctl_led
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
The ability to do 'sudo grub-reboot' depends on the use-case. In my case, the docker jobs were started via crontab, and the machine didn't crash completely, so I was able to login. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP:
[Kernel-packages] [Bug 1978296] 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 1978296 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/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Incomplete Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
[Kernel-packages] [Bug 1978296] Re: System hang with kernel general protection fault
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1978296 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) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: New Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX:
[Kernel-packages] [Bug 1978296] [NEW] System hang with kernel general protection fault
You have been subscribed to a public bug: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15: 7f6d61d7af40 Modules linked in: uhid ccm rfcomm nvidia_uvm(PO) cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi intel_tcc_cooling snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_ctl_led snd_soc_hdac_hda x86_pkg_temp_thermal snd_hda_ext_core intel_powerclamp snd_hda_codec_realtek snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_generic soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine mei_hdcp
[Kernel-packages] [Bug 1967205] Re: Lenovo laptop doesn't wake from sleep with kernel newer than 5.13.0-27-generic
I may have the same or related issue after upgrading to 22.04 on Lenovo Carbon X1 4th gen. Not only does it not wake up from sleep, but it doesn't even shut down properly. The screen switches off, but the keyboard lights are still on and the battery keeps draining so I presume other parts of hardware are still on as well. When it goes to sleep it looks similar, but also the power button pulsates indicating sleep mode. It just doesn't wake up. Had no problem with 20.04, also Windows can sleep and shut down properly on the same machine. Couldn't see anything obvious in journalctl during the shutdown, but I'll attach some excerpts below anyway. Example end of shutdown log in journalct: ``` jun 10 12:32:29 carbon systemd-journald[327]: Journal stopped jun 10 12:32:29 carbon systemd-shutdown[1]: Sending SIGTERM to remaining processes... jun 10 12:32:29 carbon systemd-shutdown[1]: Syncing filesystems and block devices. jun 10 12:32:29 carbon systemd[1]: Shutting down. jun 10 12:32:29 carbon systemd[1]: Reached target System Power Off. jun 10 12:32:29 carbon systemd[1]: Finished System Power Off. jun 10 12:32:29 carbon systemd[1]: systemd-poweroff.service: Deactivated successfully. jun 10 12:32:29 carbon systemd[1]: Reached target Late Shutdown Services. jun 10 12:32:29 carbon systemd[1]: Reached target Unmount All Filesystems. ``` Example end of suspend log in journalctl: ``` jun 10 12:51:02 carbon kernel: PM: suspend entry (deep) jun 10 12:51:02 carbon systemd-sleep[6398]: Entering sleep state 'suspend'... jun 10 12:51:02 carbon systemd[1]: Finished Record successful boot for GRUB. jun 10 12:51:02 carbon systemd[1]: grub-common.service: Deactivated successfully. jun 10 12:51:02 carbon systemd[1]: Starting System Suspend... jun 10 12:51:02 carbon systemd[1]: Starting Record successful boot for GRUB... jun 10 12:51:01 carbon systemd[1]: Reached target Sleep. ``` Let me know if I can provide any additional information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967205 Title: Lenovo laptop doesn't wake from sleep with kernel newer than 5.13.0-27-generic Status in linux package in Ubuntu: Confirmed Bug description: Issue: When closing the lid, my Lenovo 6 laptop goes to sleep, but when opening the lid the laptop will not wake from sleep when using a kernel newer than 5.13.0-27-generic. Pressing keys or the power button also does not wake the laptop from sleep. Expected behavior: The laptop should wake from sleep when opening the laptop lid when using the newest kernel. Steps to reproduce: 1. Boot laptop using kernel 5.13.0-27-generic 2. Close lid to put laptop to sleep 3. Open laptop lid and see laptop resume from sleep 4. Boot laptop with kernel newer than 5.13.0-27-generic 5. Close lid to put laptop to sleep 6. Open laptop lid and see laptop never resumes from sleep Work around: Hold the power button until laptop powers off. Press the power button again to power on the laptop Release: Ubuntu 21.10 Machine: Lenovo Yoga 6 laptop ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-39-generic 5.13.0-39.44 ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cale 1963 F pulseaudio /dev/snd/controlC2: cale 1963 F pulseaudio /dev/snd/controlC0: cale 1963 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 30 21:50:57 2022 InstallationDate: Installed on 2021-12-06 (114 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 82ND ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=UUID=5f98fca4-658f-4f22-8c2b-f320c086f693 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-39-generic N/A linux-backports-modules-5.13.0-39-generic N/A linux-firmware 1.201.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: H6CN10WW(V1.03) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 6 13ALC6 dmi.ec.firmware.release: 1.10 dmi.modalias:
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
Not sure if it will work on GCP but in Azure you hold escape to get into Grub while the system is booting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] RAX: RBX:
[Kernel-packages] [Bug 1967493] Re: pl2303 serial adapter not recognized
Thanks for the test! I will SRU this to our kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967493 Title: pl2303 serial adapter not recognized Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: Incomplete Bug description: Hi After upgrading the Linux kernel from 5.11.0-27 to 5.13.0-37 a device that uses a pl2303 usb serial chip no longer works. This seems very similar to bug 1959110, and according to that it should be fixed, but somehow it's not. # uname -a Linux GAU23LD04 5.13.0-37-generic #42~20.04.1-Ubuntu SMP Tue Mar 15 15:44:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # journalctl -b -k -g pl2303 -o cat usbcore: registered new interface driver pl2303 usbserial: USB Serial support registered for pl2303 pl2303 1-12:1.0: pl2303 converter detected pl2303 1-12:1.0: unknown device type, please report to linux-...@vger.kernel.org # udevadm info /sys/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0 P: /devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0 L: 0 E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0 E: DEVTYPE=usb_interface E: PRODUCT=67b/2303/300 E: TYPE=0/0/0 E: INTERFACE=255/0/0 E: MODALIAS=usb:v067Bp2303d0300dc00dsc00dp00icFFisc00ip00in00 E: SUBSYSTEM=usb E: USEC_INITIALIZED=56177916 E: ID_VENDOR_FROM_DATABASE=Prolific Technology, Inc. E: ID_MODEL_FROM_DATABASE=PL2303 Serial Port E: ID_PATH=pci-:00:14.0-usb-0:12:1.0 E: ID_PATH_TAG=pci-_00_14_0-usb-0_12_1_0 E: ID_MM_TTY_MANUAL_SCAN_ONLY=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
i'm intrigued, how do you 'sudo grub-reboot' when the machine is crashed? And if anyone knows how to get the grub boot menu to respond to the keyboard over the serial console on GCP that'd be great, as it would have having to attach the disk to another instance to change the boot kernel or options -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5
[Kernel-packages] [Bug 1976511] Re: kernel taint ( warning ) caused by smpboot.c: on 5.4.0
@zhanglei-mao have you tried to update the kernel? Does it still happen also with a more recent 5.4? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1976511 Title: kernel taint ( warning ) caused by smpboot.c: on 5.4.0 Status in linux package in Ubuntu: Confirmed Bug description: Apr 6 02:33:31 G292-280 kernel: [0.007531] [ cut here ] Apr 6 02:33:31 G292-280 kernel: [0.007531] sched: CPU #20's llc-sibling CPU #0 is not on the same node! [node: 1 != 0]. Ignoring dependency. Apr 6 02:33:31 G292-280 kernel: [0.007531] WARNING: CPU: 20 PID: 0 at /build/linux-hwe-5.4-9Mb2g5/linux-hwe-5.4-5.4.0/arch/x86/kernel/smpboot.c:426 topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Modules linked in: Apr 6 02:33:31 G292-280 kernel: [0.007531] CPU: 20 PID: 0 Comm: swapper/20 Not tainted 5.4.0-107-generic #121~18.04.1-Ubuntu Apr 6 02:33:31 G292-280 kernel: [0.007531] Hardware name: GIGABYTE G292-280-00/MG52-G20-00, BIOS F02 10/28/2021 Apr 6 02:33:31 G292-280 kernel: [0.007531] RIP: 0010:topology_sane.isra.9+0x6c/0x70 Apr 6 02:33:31 G292-280 kernel: [0.007531] Code: 41 5c 5d c3 80 3d 1e 75 ba 01 00 75 ec 89 f1 41 89 d9 89 fe 45 89 e0 48 c7 c7 b8 00 b4 a6 c6 05 04 75 ba 01 01 e8 b4 c7 03 00 <0f> 0b eb cb 0f 1f 44 00 00 55 0f b6 05 a3 8d f0 01 c6 05 9c 8d f0 Apr 6 02:33:31 G292-280 kernel: [0.007531] RSP: :b76b58e17eb8 EFLAGS: 00010086 Apr 6 02:33:31 G292-280 kernel: [0.007531] RAX: RBX: RCX: a7264e88 Apr 6 02:33:31 G292-280 kernel: [0.007531] RDX: a7264e88 RSI: 0096 RDI: 0046 Apr 6 02:33:31 G292-280 kernel: [0.007531] RBP: b76b58e17ec8 R08: R09: 0002f680 Apr 6 02:33:31 G292-280 kernel: [0.007531] R10: 8b69bf80 R11: 02c0 R12: 0001 Apr 6 02:33:31 G292-280 kernel: [0.007531] R13: 0014 R14: 0014 R15: 0002 Apr 6 02:33:31 G292-280 kernel: [0.007531] FS: () GS:8b69bf80() knlGS: Apr 6 02:33:31 G292-280 kernel: [0.007531] CS: 0010 DS: ES: CR0: 80050033 Apr 6 02:33:31 G292-280 kernel: [0.007531] CR2: CR3: 007ee1a0a001 CR4: 00760ee0 Apr 6 02:33:31 G292-280 kernel: [0.007531] DR0: DR1: DR2: Apr 6 02:33:31 G292-280 kernel: [0.007531] DR3: DR6: fffe0ff0 DR7: 0400 Apr 6 02:33:31 G292-280 kernel: [0.007531] PKRU: Apr 6 02:33:31 G292-280 kernel: [0.007531] Call Trace: Apr 6 02:33:31 G292-280 kernel: [0.007531] set_cpu_sibling_map+0x14f/0x600 Apr 6 02:33:31 G292-280 kernel: [0.007531] start_secondary+0x6e/0x1c0 Apr 6 02:33:31 G292-280 kernel: [0.007531] secondary_startup_64+0xa4/0xb0 Apr 6 02:33:31 G292-280 kernel: [0.007531] ---[ end trace 789d1f3abd3d96d4 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976511/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929209] Re: [i915] external monitor goes black for several seconds at a time, randomly
See also bug 1975872 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929209 Title: [i915] external monitor goes black for several seconds at a time, randomly Status in linux package in Ubuntu: Confirmed Bug description: At times it is completely debilitating; at other times it does not happen for hours. The physical connections are clean and solid. I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:56:04 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (847 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978297] [NEW] [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211
Public bug reported: [Impact] When bootup Jammy kernel, it shows callrace: kernel: kernel: UBSAN: invalid-load in /home/u/aaron/bionic/net/mac80211/status.c:1164:21 kernel: load of value 216 is not a valid value for type '_Bool' kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 5.15.36+ #12 kernel: Hardware name: LENOVO 21D2SIT061/21D2SIT061, BIOS N3GET30W (1.11 ) 05/27/2022 kernel: Call Trace: kernel: kernel: dump_stack_lvl+0x4a/0x5f kernel: dump_stack+0x10/0x12 kernel: ubsan_epilogue+0x9/0x45 kernel: __ubsan_handle_load_invalid_value.cold+0x44/0x49 kernel: ieee80211_tx_status_ext.cold+0x1e/0xb0 [mac80211] kernel: ? percpu_ref_kill_and_confirm+0xd0/0xd0 kernel: ? rht_key_get_hash.isra.0+0x19/0x20 [mac80211] kernel: ? sta_info_hash_lookup+0xac/0x100 [mac80211] kernel: ieee80211_tx_status+0x72/0xa0 [mac80211] kernel: ieee80211_tasklet_handler+0xa2/0xd0 [mac80211] kernel: tasklet_action_common.constprop.0+0xc0/0xf0 kernel: tasklet_action+0x22/0x30 kernel: __do_softirq+0xd9/0x2e3 kernel: irq_exit_rcu+0x8c/0xb0 kernel: common_interrupt+0x8a/0xa0 kernel: kernel: kernel: asm_common_interrupt+0x1e/0x40 kernel: RIP: 0010:cpuidle_enter_state+0xd9/0x620 kernel: Code: 3d b4 85 3d 5c e8 57 a7 6b ff 49 89 c7 0f 1f 44 00 00 31 ff e8 a8 b3 6b ff 80 7d d0> kernel: RSP: 0018:9e2dc01f7e38 EFLAGS: 0246 kernel: RAX: 8dfdb6870b00 RBX: 8df6c3ab6c00 RCX: 00023cd33784 kernel: RDX: 00023d103fa8 RSI: 00023cd33784 RDI: kernel: RBP: 9e2dc01f7e88 R08: 00023cd33d63 R09: 000aae60 kernel: R10: 0004 R11: 071c71c71c71c71c R12: a4ce65a0 kernel: R13: 0003 R14: 0003 R15: 00023cd33d63 kernel: ? cpuidle_enter_state+0xc8/0x620 kernel: ? sched_clock_local+0x13/0x90 kernel: cpuidle_enter+0x2e/0x40 kernel: do_idle+0x203/0x2a0 kernel: cpu_startup_entry+0x20/0x30 kernel: start_secondary+0x12a/0x180 kernel: secondary_startup_64_no_verify+0xc2/0xcb kernel: kernel: [Fix] The size of the status_driver_data field was not adjusted when the is_valid_ack_signal field was added. Adjust the struct size accordingly. [Test] Verified on hardware, no error. [Where problems could occur] Low risk, It may break wifi driver. Minor changes in title of "Copyright" when backport. ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Description changed: [Impact] When bootup Jammy kernel, it shows callrace: kernel: kernel: UBSAN: invalid-load in /home/u/aaron/bionic/net/mac80211/status.c:1164:21 kernel: load of value 216 is not a valid value for type '_Bool' kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 5.15.36+ #12 kernel: Hardware name: LENOVO 21D2SIT061/21D2SIT061, BIOS N3GET30W (1.11 ) 05/27/2022 kernel: Call Trace: kernel: kernel: dump_stack_lvl+0x4a/0x5f kernel: dump_stack+0x10/0x12 kernel: ubsan_epilogue+0x9/0x45 kernel: __ubsan_handle_load_invalid_value.cold+0x44/0x49 kernel: ieee80211_tx_status_ext.cold+0x1e/0xb0 [mac80211] kernel: ? percpu_ref_kill_and_confirm+0xd0/0xd0 kernel: ? rht_key_get_hash.isra.0+0x19/0x20 [mac80211] kernel: ? sta_info_hash_lookup+0xac/0x100 [mac80211] kernel: ieee80211_tx_status+0x72/0xa0 [mac80211] kernel: ieee80211_tasklet_handler+0xa2/0xd0 [mac80211] kernel: tasklet_action_common.constprop.0+0xc0/0xf0 kernel: tasklet_action+0x22/0x30 kernel: __do_softirq+0xd9/0x2e3 kernel: irq_exit_rcu+0x8c/0xb0 kernel: common_interrupt+0x8a/0xa0 kernel: kernel: kernel: asm_common_interrupt+0x1e/0x40 kernel: RIP: 0010:cpuidle_enter_state+0xd9/0x620 kernel: Code: 3d b4 85 3d 5c e8 57 a7 6b ff 49 89 c7 0f 1f 44 00 00 31 ff e8 a8 b3 6b ff 80 7d d0> kernel: RSP: 0018:9e2dc01f7e38 EFLAGS: 0246 kernel: RAX: 8dfdb6870b00 RBX: 8df6c3ab6c00 RCX: 00023cd33784 kernel: RDX: 00023d103fa8 RSI: 00023cd33784 RDI: kernel: RBP: 9e2dc01f7e88 R08: 00023cd33d63 R09:
[Kernel-packages] [Bug 1977815] Re: ADLP AX211 iwlwifi firmware crash after resume
Invalid this bug due to the issue can not be reproduced after swap wifi module. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1977815 Title: ADLP AX211 iwlwifi firmware crash after resume Status in linux-firmware package in Ubuntu: Invalid Bug description: On Intel ADL-P platform with AX211 Wi-Fi, encounter firmware crash after resume from suspend. wifi failed to connect after the below message. [ 5525.553757] iwlwifi :00:14.3: Queue 2 is stuck 2 3 [ 5525.554875] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [ 5525.555117] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 5525.555122] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 [ 5525.555129] iwlwifi :00:14.3: Loaded firmware version: 67.8f59b80b.0 so-a0-gf-a0-67.ucode [ 5525.555135] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [ 5525.555141] iwlwifi :00:14.3: 0x02F3 | trm_hw_status0 [ 5525.555145] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 5525.555149] iwlwifi :00:14.3: 0x004D9EF2 | branchlink2 [ 5525.555153] iwlwifi :00:14.3: 0x004D960E | interruptlink1 [ 5525.555157] iwlwifi :00:14.3: 0x004D960E | interruptlink2 [ 5525.555160] iwlwifi :00:14.3: 0x004C6C34 | data1 [ 5525.555163] iwlwifi :00:14.3: 0x0100 | data2 [ 5525.555167] iwlwifi :00:14.3: 0x | data3 [ 5525.555170] iwlwifi :00:14.3: 0x1AC138AE | beacon time [ 5525.555174] iwlwifi :00:14.3: 0xFA1F775A | tsf low [ 5525.555177] iwlwifi :00:14.3: 0x0002 | tsf hi [ 5525.555181] iwlwifi :00:14.3: 0x | time gp1 [ 5525.555184] iwlwifi :00:14.3: 0x029BB566 | time gp2 [ 5525.555188] iwlwifi :00:14.3: 0x0001 | uCode revision type [ 5525.555191] iwlwifi :00:14.3: 0x0043 | uCode version major [ 5525.555194] iwlwifi :00:14.3: 0x8F59B80B | uCode version minor [ 5525.555198] iwlwifi :00:14.3: 0x0370 | hw version [ 5525.555202] iwlwifi :00:14.3: 0x00489002 | board version --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-qyburn+X170 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-06-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. wlp0s20f3 no wireless extensions. enx00e04f8238df no wireless extensions. MachineType: Dell Inc. Inspiron 16 5620 Package: linux-firmware 1.187.31 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1040-oem root=UUID=202d0ced-071f-4d95-a481-17b8e1078844 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-1040.44-oem 5.14.21 RelatedPackageVersions: linux-restricted-modules-5.14.0-1040-oem N/A linux-backports-modules-5.14.0-1040-oem N/A linux-firmware 1.187.31 Tags: focal Uname: Linux 5.14.0-1040-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0Q901G dmi.board.vendor: Dell Inc. dmi.board.version: D02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd04/21/2022:br1.1:svnDellInc.:pnInspiron165620:pvr:rvnDellInc.:rn0Q901G:rvrD02:cvnDellInc.:ct10:cvr:sku0BAA: dmi.product.family: Inspiron dmi.product.name: Inspiron 16 5620 dmi.product.sku: 0BAA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1977815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977946] Re: README points to non-existent URL
The attachment "1-0.12.16ubuntu1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1977946 Title: README points to non-existent URL Status in ubuntu-fan package in Ubuntu: Fix Committed Bug description: /usr/share/doc/ubuntu-fan/README.gz (ubuntu-fan/README) reads: "More information on the Fan, including more detailed configuration information, can be found at http://www.ubuntu.com/fan.; However, the aforementioned URL (with and without trailing dot) does not exist. Is this supposed to point to https://wiki.ubuntu.com/FanNetworking instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1977946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978293] [NEW] nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: The error sometimes occurs randomly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-48-generic Date: Fri Jun 10 10:15:44 2022 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-450:450.119.03-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/450.119.03/build/nvidia-drm/nvidia-drm-crtc.c:234:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2020-11-23 (563 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 450.119.03-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1978293 Title: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: The error sometimes occurs randomly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-48-generic Date: Fri Jun 10 10:15:44 2022 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-450:450.119.03-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/450.119.03/build/nvidia-drm/nvidia-drm-crtc.c:234:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2020-11-23 (563 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 450.119.03-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-kernel-source-450 450.119.03-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1978293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
I had limited success with "grub-reboot 2", but the following worked fine for me on an AWS EC2 running Ubuntu 20.04.2 sudo grub-reboot "Advanced options for Ubuntu>Ubuntu, with Linux 5.13.0-1025-aws" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws-5.13 package in Ubuntu: Confirmed Status in linux-azure-5.13 package in Ubuntu: Confirmed Status in linux-gcp-5.13 package in Ubuntu: Confirmed Status in linux-intel-iotg-5.15 package in Ubuntu: Confirmed Status in linux-oracle-5.13 package in Ubuntu: Confirmed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-azure-5.13 source package in Focal: Fix Committed Status in linux-gcp-5.13 source package in Focal: Fix Committed Status in linux-intel-iotg-5.15 source package in Focal: Won't Fix Status in linux-oracle-5.13 source package in Focal: Fix Committed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP:
[Kernel-packages] [Bug 1967493] Re: pl2303 serial adapter not recognized
I've tested on the test kernel, and it's working perfectly - Thanks! # uname -a Linux GAU23LD12 5.13.0-47-generic #52~20.04.1+lp1967493 SMP Mon Jun 6 06:43:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967493 Title: pl2303 serial adapter not recognized Status in linux package in Ubuntu: Incomplete Status in linux source package in Impish: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: Incomplete Bug description: Hi After upgrading the Linux kernel from 5.11.0-27 to 5.13.0-37 a device that uses a pl2303 usb serial chip no longer works. This seems very similar to bug 1959110, and according to that it should be fixed, but somehow it's not. # uname -a Linux GAU23LD04 5.13.0-37-generic #42~20.04.1-Ubuntu SMP Tue Mar 15 15:44:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux # journalctl -b -k -g pl2303 -o cat usbcore: registered new interface driver pl2303 usbserial: USB Serial support registered for pl2303 pl2303 1-12:1.0: pl2303 converter detected pl2303 1-12:1.0: unknown device type, please report to linux-...@vger.kernel.org # udevadm info /sys/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0 P: /devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0 L: 0 E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0 E: DEVTYPE=usb_interface E: PRODUCT=67b/2303/300 E: TYPE=0/0/0 E: INTERFACE=255/0/0 E: MODALIAS=usb:v067Bp2303d0300dc00dsc00dp00icFFisc00ip00in00 E: SUBSYSTEM=usb E: USEC_INITIALIZED=56177916 E: ID_VENDOR_FROM_DATABASE=Prolific Technology, Inc. E: ID_MODEL_FROM_DATABASE=PL2303 Serial Port E: ID_PATH=pci-:00:14.0-usb-0:12:1.0 E: ID_PATH_TAG=pci-_00_14_0-usb-0_12_1_0 E: ID_MM_TTY_MANUAL_SCAN_ONLY=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978289] [NEW] The BCM 4313 Wireless Doesnt work
Public bug reported: udo dmidecode -s bios-version sudo dmidecode -s bios-release-date 12:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01) Subsystem: Dell Inspiron M5010 / XPS 8300 [1028:0010] Physical Slot: 0-1 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: wl Description:Ubuntu 22.04 LTS Release:22.04 Linux lucas-inspironn4030 5.15.0-37-generic #39-Ubuntu SMP Wed Jun 1 19:16:45 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux A07 03/23/2011 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 10 09:23:11 2022 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1978289 Title: The BCM 4313 Wireless Doesnt work Status in bcmwl package in Ubuntu: New Bug description: udo dmidecode -s bios-version sudo dmidecode -s bios-release-date 12:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01) Subsystem: Dell Inspiron M5010 / XPS 8300 [1028:0010] Physical Slot: 0-1 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: wl Description:Ubuntu 22.04 LTS Release:22.04 Linux lucas-inspironn4030 5.15.0-37-generic #39-Ubuntu SMP Wed Jun 1 19:16:45 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux A07 03/23/2011 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 10 09:23:11 2022 InstallationDate: Installed on 2022-06-09 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1978289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978087] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
Hardware problems. From the log:
[ 444.432309] ata1.00: exception Emask 0x0 SAct 0xc00f SErr 0x5 action 0x0
[ 444.432328] ata1.00: irq_stat 0x4001
[ 444.432335] ata1: SError: { PHYRdyChg CommWake }
[ 444.432345] ata1.00: failed command: WRITE FPDMA QUEUED
[ 444.432351] ata1.00: cmd 61/40:00:00:59:22/05:00:2f:00:00/40 tag 0 ncq dma
688128 out
res 41/40:78:a0:14:00/00:00:00:00:00/40 Emask 0x9
(media error)
[ 444.432373] ata1.00: status: { DRDY ERR }
[ 444.432379] ata1.00: error: { UNC }
[ 444.432387] ata1.00: failed command: WRITE FPDMA QUEUED
[ 444.432392] ata1.00: cmd 61/c0:08:40:5e:22/02:00:2f:00:00/40 tag 1 ncq dma
360448 out
res 41/40:78:a0:14:00/00:00:00:00:00/40 Emask 0x9
(media error)
[ 444.432411] ata1.00: status: { DRDY ERR }
[ 444.432417] ata1.00: error: { UNC }
[ 444.432424] ata1.00: failed command: WRITE FPDMA QUEUED
[ 444.432429] ata1.00: cmd 61/40:10:00:61:22/05:00:2f:00:00/40 tag 2 ncq dma
688128 out
res 41/40:78:a0:14:00/00:00:00:00:00/40 Emask 0x9
(media error)
[ 444.432445] ata1.00: status: { DRDY ERR }
[ 444.432450] ata1.00: error: { UNC }
[ 444.432457] ata1.00: failed command: WRITE FPDMA QUEUED
[ 444.432462] ata1.00: cmd 61/c0:18:40:66:22/02:00:2f:00:00/40 tag 3 ncq dma
360448 out
res 41/40:78:a0:14:00/00:00:00:00:00/40 Emask 0x9
(media error)
[ 444.432478] ata1.00: status: { DRDY ERR }
[ 444.432483] ata1.00: error: { UNC }
[ 444.432490] ata1.00: failed command: READ FPDMA QUEUED
[ 444.432494] ata1.00: cmd 60/00:70:a0:14:00/01:00:00:00:00/40 tag 14 ncq dma
131072 in
res 41/40:00:a0:14:00/00:01:00:00:00/40 Emask 0x409
(media error)
[ 444.432510] ata1.00: status: { DRDY ERR }
[ 444.432516] ata1.00: error: { UNC }
[ 444.432522] ata1.00: failed command: READ FPDMA QUEUED
[ 444.432526] ata1.00: cmd 60/00:78:a0:15:00/01:00:00:00:00/40 tag 15 ncq dma
131072 in
res 41/40:78:a0:14:00/00:00:00:00:00/40 Emask 0x9
(media error)
[ 444.432541] ata1.00: status: { DRDY ERR }
[ 444.432546] ata1.00: error: { UNC }
[ 444.435750] ata1.00: configured for UDMA/100
[ 444.435804] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_OK cmd_age=3s
[ 444.435812] sd 0:0:0:0: [sda] tag#0 Sense Key : Medium Error [current]
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1978087
Title:
package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to
install/upgrade: installed linux-firmware package post-installation
script subprocess returned error exit status 1
Status in linux-firmware package in Ubuntu:
Invalid
Bug description:
not installed
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-firmware 20220329.git681281e4-0ubuntu3.2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: arsss 1298 F pulseaudio
/dev/snd/controlC0: arsss 1298 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Jun 9 17:19:39 2022
Dependencies: firmware-sof-signed 2.0-1ubuntu3
ErrorMessage: installed linux-firmware package post-installation script
subprocess returned error exit status 1
InstallationDate: Installed on 2022-06-09 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: LENOVO 20369
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic
root=UUID=2a960677-859f-46a6-9471-a9c94e8b41bd ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal,
3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.06-2ubuntu7
SourcePackage: linux-firmware
Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to
install/upgrade: installed linux-firmware package post-installation script
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2014
dmi.bios.release: 0.29
dmi.bios.vendor: LENOVO
dmi.bios.version: 9ACN29WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lancer 4A2
dmi.board.vendor: LENOVO
dmi.board.version: NANANANANO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G40-70
dmi.ec.firmware.release: 0.29
dmi.modalias:
[Kernel-packages] [Bug 1977946] Re: README points to non-existent URL
Link changed to the proposed wiki. pbuilder succeeded, README updated. ** Patch added: "1-0.12.16ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1977946/+attachment/5596248/+files/1-0.12.16ubuntu1.debdiff ** Changed in: ubuntu-fan (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1977946 Title: README points to non-existent URL Status in ubuntu-fan package in Ubuntu: Fix Committed Bug description: /usr/share/doc/ubuntu-fan/README.gz (ubuntu-fan/README) reads: "More information on the Fan, including more detailed configuration information, can be found at http://www.ubuntu.com/fan.; However, the aforementioned URL (with and without trailing dot) does not exist. Is this supposed to point to https://wiki.ubuntu.com/FanNetworking instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1977946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
