[Kernel-packages] [Bug 2002938] 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/2002938 Title: Logitech webcam crashed the kernel Status in linux package in Ubuntu: Confirmed Bug description: This happens during a "Zoom" video conference call done within a virtual machine. Both the host and the guest OSes are Ubuntu 22.04. A few minutes after the video call started audio is lost, and a few seconds later the (guest) system crashes. The webcam used is a USB Logitech Webcam C270 which is connected to the VM as a USB passthrough (i.e. using the "Add new virtual hardware => USB host device" in virt-manager). Note that the "dmesg" attached is probably irrelevant so I attached the output of "journalctl --boot=..." of the relevant session. The kernel crash can be seen near the end of the log, look for the following lines: Jan 10 19:54:12 yariv-encrypted-ubuntu kernel: usb 1-4: cannot submit urb (err = -27) Jan 10 19:54:13 yariv-encrypted-ubuntu kernel: usb 1-4: timeout: still 1 active urbs on EP #86 Jan 10 19:54:13 yariv-encrypted-ubuntu kernel: [ cut here ] Jan 10 19:54:13 yariv-encrypted-ubuntu kernel: URB submitted while active ... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yariv 1897 F pulseaudio /dev/snd/controlC0: yariv 1897 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 09:06:56 2023 HibernationDevice: RESUME=UUID=1c38618d-3590-45c4-b960-ca9d157ad22f InstallationDate: Installed on 2019-02-26 (1419 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. ens3 no wireless extensions. docker0 no wireless extensions. MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-58-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-12 (95 days ago) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.15.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.15.0-1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:sku: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002938] [NEW] Logitech webcam crashed the kernel
Public bug reported: This happens during a "Zoom" video conference call done within a virtual machine. Both the host and the guest OSes are Ubuntu 22.04. A few minutes after the video call started audio is lost, and a few seconds later the (guest) system crashes. The webcam used is a USB Logitech Webcam C270 which is connected to the VM as a USB passthrough (i.e. using the "Add new virtual hardware => USB host device" in virt-manager). Note that the "dmesg" attached is probably irrelevant so I attached the output of "journalctl --boot=..." of the relevant session. The kernel crash can be seen near the end of the log, look for the following lines: Jan 10 19:54:12 yariv-encrypted-ubuntu kernel: usb 1-4: cannot submit urb (err = -27) Jan 10 19:54:13 yariv-encrypted-ubuntu kernel: usb 1-4: timeout: still 1 active urbs on EP #86 Jan 10 19:54:13 yariv-encrypted-ubuntu kernel: [ cut here ] Jan 10 19:54:13 yariv-encrypted-ubuntu kernel: URB submitted while active ... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yariv 1897 F pulseaudio /dev/snd/controlC0: yariv 1897 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 09:06:56 2023 HibernationDevice: RESUME=UUID=1c38618d-3590-45c4-b960-ca9d157ad22f InstallationDate: Installed on 2019-02-26 (1419 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. ens3 no wireless extensions. docker0 no wireless extensions. MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-58-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-12 (95 days ago) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.15.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.15.0-1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:sku: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "journalctl of the relevant boot session" https://bugs.launchpad.net/bugs/2002938/+attachment/5641536/+files/freeze_issue.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002938 Title: Logitech webcam crashed the kernel Status in linux package in Ubuntu: New Bug description: This happens during a "Zoom" video conference call done within a virtual machine. Both the host and the guest OSes are Ubuntu 22.04. A few minutes after the video call started audio is lost, and a few seconds later the (guest) system crashes. The webcam used is a USB Logitech Webcam C270 which is connected to the VM as a USB passthrough (i.e. using the "Add new virtual hardware => USB host device" in virt-manager). Note that the "dmesg" attached is probably irrelevant so I attached the output of "journalctl --boot=..." of the relevant session. The kernel crash can be seen near the end of the log, look for the following lines: Jan 10 19:54:12 yariv-encrypted-ubuntu kernel: usb 1-4: cannot submit urb (err = -27) Jan 10 19:54:13 yariv-encrypted-ubuntu kernel: usb 1-4: timeout: still 1 active urbs on EP #86 Jan 10 19:54:13 yariv-encrypted-ubuntu kernel: [ cut here ] Jan 10 19:54:13 yariv-encrypted-ubuntu kernel: URB submitted while active ... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yariv 1897 F pulseaudio /dev/snd/controlC0: yariv 1897 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 09:06:56 2023 HibernationDevice: RESUME=UUID=1c38618d-3590-45c4-b960-ca9d157ad22f InstallationDate: Installed on 2019-02-26
[Kernel-packages] [Bug 2001599] Re: Lost display on built-in monitor after suspend
** Tags added: originate-from-2000192 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2001599 Title: Lost display on built-in monitor after suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some laptops, the eDP blinking slowly after resuming from S3 [Fix] The series of patches which are in drp-tip fix the isue https://patchwork.freedesktop.org/series/110693/ [Test] ODM and I confirmed the issue is fixed after the patches have been applied. [Where problems may occur] This series of patches fixes a dedicate issue and change the power sequence for the eDP panel. eDP panel may stay blank if the rules are wrong. Our QA will help us to verify this kind of issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2001599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876449] Re: Apple external Trackpad event timestamps are jittery
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876449 Title: Apple external Trackpad event timestamps are jittery Status in linux package in Ubuntu: Fix Released Bug description: Using a vanilla installation of Ubuntu 20.04, the timestamps of input events from my Apple "Magic Trackpad" - 1st generation, connected over Bluetooth - are jittery. This is a regression, the timestamps were fine when using Ubuntu 19.10. I bisected the bug. - The problem starts with upstream kernel commit 3b51c44bd693 ("Input: allow drivers specify timestamp for input events"). After that commit, the same timestamp is always emitted. - This was partially fixed in commit 4370b231d100 ("Input: reset device timestamp on sync"), however ever since then the timestamps are jittery. The problem still exists in the current upstream 'master' (commit c45e8bccecaf). The following patch fixes the bug, however this is obviously a hack. It effectively reverts commit 3b51c44bd693: diff --git a/drivers/input/input.c b/drivers/input/input.c index 3cfd2c18eebd..8890195547d6 100644 --- a/drivers/input/input.c +++ b/drivers/input/input.c @@ -1958,7 +1958,7 @@ ktime_t *input_get_timestamp(struct input_dev *dev) { const ktime_t invalid_timestamp = ktime_set(0, 0); - if (!ktime_compare(dev->timestamp[INPUT_CLK_MONO], invalid_timestamp)) + // if (!ktime_compare(dev->timestamp[INPUT_CLK_MONO], invalid_timestamp)) input_set_timestamp(dev, ktime_get()); return dev->timestamp; Steps to reproduce -- I used the following script as a reproducer. It relies on libinput- debug-events. This script measures the time delta between consecutive input events, then prints a "histogram" of these deltas. #!/bin/bash # log file name logFile=${1:-~/Downloads/`uname -r`} echo logFile=$logFile if [[ "$1" == '' ]]; then echo record # log some events sudo libinput debug-events | grep POINTER | tee $logFile fi # process the results lastN=0 for f in `cat $logFile | awk '{print $3}' | sed "s/s//g" | sed "s/+//g"`; do echo "$f-$lastN" | bc; lastN=$f; done | sort | uniq -c 1. Pair an external Apple Trackpad over Blutooth. 2. Run the above script 3. Move your finger in circles on the touchpad for a few seconds 4. Press ctrl+c An example output of this script before the regression -- 2 .010 371 .011 127 .012 1 .876 The above output means that: 2 times the delta was 10ms, 371 times 11ms, 127 times 12ms and 1 time 876ms. This corresponds well with the Trackpad's ~90Hz polling rate. An example output of this script after the regression - 3 .003 12 .004 16 .005 14 .006 21 .007 16 .008 20 .009 13 .010 359 .011 47 .012 20 .013 17 .014 21 .015 14 .016 16 .017 15 .018 2 .019 1 .020 38 .022 21 .023 1 1.060 I suspect that other input devices might be affected as well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-28-generic 5.4.0-28.32 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yariv 1783 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 2 13:58:34 2020 InstallationDate: Installed on 2019-07-13 (293 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=6deee348-bb50-4b88-837b-108413e4d8f2 ro quiet splash btusb.enable_autosuspend=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-28 (3 days ago) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22g dmi.board.asset.tag: Default string dmi.board.name: Z170X-UD5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops
** Tags added: jellyfish-edge-staging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2002373 Title: Mic Mute LED doesn't work on DMIC laptops Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Jammy: Confirmed Status in alsa-ucm-conf source package in Kinetic: Confirmed Status in alsa-ucm-conf source package in Lunar: Confirmed Bug description: [Impact] Mic mute LED doesn't work on Intel-based HP laptops. [Fix] Due to recent change on how kernel creates sound LEDs, there are two captures are registered, one from SoF and one from HDA. The SoF one is the "real" capture system uses. Since physical LED only gets light up when _all_ captures are muted, detach the HDA one so micmute LED only need to consider SoF capture's mute status. [Test] The mic mute LED works again on DMIC laptops. The legacy HDA systems are unaffected. [Where problems could occur] Theoretically the system may have more than two internal captures registered, then disabling one will not be enough. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973574] Re: The system has become much choppier
Are you still experiencing "choppy" performance? If so then please confirm the current Ubuntu version you are using and give some examples (perhaps with video) of what is choppy. ** Package changed: linux (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => 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/1973574 Title: The system has become much choppier Status in Ubuntu: Incomplete Bug description: The system has been getting choppy and the last upgrade is a failure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-110-generic 5.4.0-110.124 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 16 12:59:42 2022 InstallationDate: Installed on 2021-10-27 (200 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-110-generic root=UUID=5b9e5e8a-d7f3-42fd-9895-dd751e39ce69 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-110-generic N/A linux-backports-modules-5.4.0-110-generic N/A linux-firmware 1.187.30 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd01/25/2018:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 2EY84PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-10-28T20:41:46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1973574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973574] Re: The system has become much choppier and no audio is being heard
Audio has been reported in bug 1973575. ** Summary changed: - The system has become much choppier and no audio is being heard + The system has become much choppier ** Description changed: - The system has been getting choppy and the last upgrade is a - failure.Also the sound is not coming even though the video is being - played. + The system has been getting choppy and the last upgrade is a failure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-110-generic 5.4.0-110.124 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 16 12:59:42 2022 InstallationDate: Installed on 2021-10-27 (200 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera - Bus 001 Device 002: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera + Bus 001 Device 002: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-110-generic root=UUID=5b9e5e8a-d7f3-42fd-9895-dd751e39ce69 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-110-generic N/A - linux-backports-modules-5.4.0-110-generic N/A - linux-firmware 1.187.30 + linux-restricted-modules-5.4.0-110-generic N/A + linux-backports-modules-5.4.0-110-generic N/A + linux-firmware 1.187.30 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd01/25/2018:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 2EY84PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.default.apport: - # set this to 0 to disable apport, or to 1 to enable it - # you can temporarily override this with - # sudo service apport start force_start=1 - enabled=0 + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 mtime.conffile..etc.default.apport: 2018-10-28T20:41:46 -- 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/1973574 Title: The system has become much choppier Status in Ubuntu: Incomplete Bug description: The system has been getting choppy and the last upgrade is a failure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-110-generic 5.4.0-110.124 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 16 12:59:42 2022 InstallationDate: Installed on 2021-10-27 (200 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2c9b
[Kernel-packages] [Bug 2002206] Re: Periodic freezing after unplugging USB-C monitor - "Enabling HDA controller" in dmesg
Does removing "pci=nommconf" help? ** Changed in: linux (Ubuntu) Status: Confirmed => 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/2002206 Title: Periodic freezing after unplugging USB-C monitor - "Enabling HDA controller" in dmesg Status in linux package in Ubuntu: Incomplete Bug description: After disconnecting an external monitor from a Thunderbolt 4 (USB-C) port *while the system is asleep*, after wake-up the system keeps on randomly freezing for 1-2 seconds. Every freeze is accompanied by an "Enabling HDA controller" kernel message: [54984.259832] nvidia :01:00.0: Enabling HDA controller [55008.355784] nvidia :01:00.0: Enabling HDA controller [55044.771722] nvidia :01:00.0: Enabling HDA controller [55069.859682] nvidia :01:00.0: Enabling HDA controller [55096.547622] nvidia :01:00.0: Enabling HDA controller [55122.243581] nvidia :01:00.0: Enabling HDA controller [55146.339543] nvidia :01:00.0: Enabling HDA controller [55168.579505] nvidia :01:00.0: Enabling HDA controller [55199.491437] nvidia :01:00.0: Enabling HDA controller Rebooting or restarting Xorg "fixes" the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-56-generic 5.15.0-56.62 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: socwatch2_15 vtsspp sep5 socperf3 pax nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: me 2469 F pulseaudio /dev/snd/controlC0: me 2469 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sat Jan 7 12:19:39 2023 InstallationDate: Installed on 2022-08-31 (128 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 04f2:b74f Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 06cb:00f9 Synaptics, Inc. Bus 001 Device 007: ID 8087:0033 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 21DE001QMH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=d4a7fdda-30e3-439b-b327-e87d7b2bc81e ro pci=nommconf PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/18/2022 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: N3JET28W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 21DE001QMH dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN3JET28W(1.12):bd10/18/2022:br1.12:efr1.8:svnLENOVO:pn21DE001QMH:pvrThinkPadX1ExtremeGen5:rvnLENOVO:rn21DE001QMH:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21DE_BU_Think_FM_ThinkPadX1ExtremeGen5: dmi.product.family: ThinkPad X1 Extreme Gen 5 dmi.product.name: 21DE001QMH dmi.product.sku: LENOVO_MT_21DE_BU_Think_FM_ThinkPad X1 Extreme Gen 5 dmi.product.version: ThinkPad X1 Extreme Gen 5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Can you please give latest mainline kernel a try: https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2-rc4/ Please attach full dmesg if the issue remains. -- 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/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-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. RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999094] Re: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28
Hints removed, closing this bug for U-K-T ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999094 Title: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Released Bug description: This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all instances. Running tests... vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents look like this: vma05 1 TPASS: [vsyscall] reported correctly vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 418325] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)): #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 #3 0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at ../sysdeps/posix/raise.c:26 #4 0x55f54287a072 in main () at vma05_vdso.c:5 vma05 1 TPASS: [vdso] backtrace complete -- while on 5.19.0-27.28 it looks like this: vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 1501] Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9b3c09226b in ?? () Thread 1 (LWP 1501): #0 0x7f9b3c09226b in ?? () Backtrace stopped: Cannot access memory at address 0x7ffc216242b0 vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Suggesting that this bug has somehow been reintroduced. Will look into this further. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999094] Re: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28
This issue didn't not happen on kinetic/linux-ibm/5.19.0-1015.16 as well. ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/1999094 Title: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Released Bug description: This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all instances. Running tests... vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents look like this: vma05 1 TPASS: [vsyscall] reported correctly vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 418325] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)): #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 #3 0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at ../sysdeps/posix/raise.c:26 #4 0x55f54287a072 in main () at vma05_vdso.c:5 vma05 1 TPASS: [vdso] backtrace complete -- while on 5.19.0-27.28 it looks like this: vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 1501] Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9b3c09226b in ?? () Thread 1 (LWP 1501): #0 0x7f9b3c09226b in ?? () Backtrace stopped: Cannot access memory at address 0x7ffc216242b0 vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Suggesting that this bug has somehow been reintroduced. Will look into this further. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999094] Re: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28
Verified with Kinetic linux-aws/5.19.0-1018.19, test passed as expected. -- 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/1999094 Title: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Released Bug description: This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all instances. Running tests... vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents look like this: vma05 1 TPASS: [vsyscall] reported correctly vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 418325] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)): #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 #3 0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at ../sysdeps/posix/raise.c:26 #4 0x55f54287a072 in main () at vma05_vdso.c:5 vma05 1 TPASS: [vdso] backtrace complete -- while on 5.19.0-27.28 it looks like this: vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 1501] Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9b3c09226b in ?? () Thread 1 (LWP 1501): #0 0x7f9b3c09226b in ?? () Backtrace stopped: Cannot access memory at address 0x7ffc216242b0 vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Suggesting that this bug has somehow been reintroduced. Will look into this further. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995173] 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/1995173 Title: Lenovo Legion 7: Cannot Control Display Brightness Status in linux package in Ubuntu: Confirmed Bug description: The device is Lenovo Legion 7. This laptop has a mux switch to switch between dynamic/hybrid or discrete graphics mode. This laptop has a high resolution with high pixel density than the other displays out there, but I don't know the exact number. Additionally, this laptop can adjust the display refresh rate between 60 and 165 Hz. --- There were 1 problem I encountered in dynamic/hybrid graphics mode: - The widgets shown were too small. Details: The resolution was correct, at 2560x1600, but all widgets shown were too small. I suspected this was due to the laptop screen high pixel density and the widget size calculation didn't make use of physical dimension, but in terms of pixel. I thought installing NVIDIA driver would fix this, but no; this worked in OpenSUSE Leap with KDE Plasma and I think it was because of the inclusion of NVIDIA OpenGL driver. The current workaround was to scale by 200% in "Display Settings", although the login screen isn't affected by the scaling at all. --- There were 3 problems I encountered in discrete graphics mode: - The widgets were are too small, like the hybrid graphics mode issue. - The DE seemed to use wrong screen refresh rate. The refresh rate was fixed at 93 Hz in the "Display Settings". Changing the refresh rate between 60 Hz and 165 Hz by Fn keys didn't update the 93 Hz in the "Display Settings". This didn't happen in the hybrid graphics mode. OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I think it may be either GNOME DE or xorg misconfigurations. - Screen brightness was fixed at 100%. Details: Screen brightness could be adjusted by the keyboard Fn keys, but the brightness was fixed at 100%. This didn't happen in the hybrid graphics mode. This is the most annoying problem and have forced me to use the hybrid graphics mode which I don't like. My first thought was either a specific NVIDIA issue or xorg misconfigurations. So I tried adding "acpi_backlight=vendor" and "nvdia.NVreg_RegistryDwords=EnableBrightnessControl=1" to GRUB, but didn't work at all. --- In discrete graphics mode, a quick "sudo journalctl -p3 -b0" showed below: Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: integrity: Problem loading X.509 certificate -65 Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20210730/psargs-330) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20210730/psparse-529) In hybrid graphics mode, "sudo journalctl -p3 -b0" output like above except that there was no: Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20210730/psargs-330) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX Open Kernel Module for x86_64 520.56.06 Release Build (dvs-builder@U16-T12-10-2) Thu Oct 6 21:33:54 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 29 18:50:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/520.56.06, 5.15.0-52-generic, x86_64: installed
[Kernel-packages] [Bug 1995173] Re: Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue
Thanks for the bug report, but please ensure you only report one issue per bug in future. ** Summary changed: - Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue + Lenovo Legion 7 Display Issues : Cannot Control Display Brightness ** Package changed: nvidia-graphics-drivers-520 (Ubuntu) => linux (Ubuntu) ** Summary changed: - Lenovo Legion 7 Display Issues : Cannot Control Display Brightness + Lenovo Legion 7: Cannot Control Display Brightness -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-520 in Ubuntu. https://bugs.launchpad.net/bugs/1995173 Title: Lenovo Legion 7: Cannot Control Display Brightness Status in linux package in Ubuntu: New Bug description: The device is Lenovo Legion 7. This laptop has a mux switch to switch between dynamic/hybrid or discrete graphics mode. This laptop has a high resolution with high pixel density than the other displays out there, but I don't know the exact number. Additionally, this laptop can adjust the display refresh rate between 60 and 165 Hz. --- There were 1 problem I encountered in dynamic/hybrid graphics mode: - The widgets shown were too small. Details: The resolution was correct, at 2560x1600, but all widgets shown were too small. I suspected this was due to the laptop screen high pixel density and the widget size calculation didn't make use of physical dimension, but in terms of pixel. I thought installing NVIDIA driver would fix this, but no; this worked in OpenSUSE Leap with KDE Plasma and I think it was because of the inclusion of NVIDIA OpenGL driver. The current workaround was to scale by 200% in "Display Settings", although the login screen isn't affected by the scaling at all. --- There were 3 problems I encountered in discrete graphics mode: - The widgets were are too small, like the hybrid graphics mode issue. - The DE seemed to use wrong screen refresh rate. The refresh rate was fixed at 93 Hz in the "Display Settings". Changing the refresh rate between 60 Hz and 165 Hz by Fn keys didn't update the 93 Hz in the "Display Settings". This didn't happen in the hybrid graphics mode. OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I think it may be either GNOME DE or xorg misconfigurations. - Screen brightness was fixed at 100%. Details: Screen brightness could be adjusted by the keyboard Fn keys, but the brightness was fixed at 100%. This didn't happen in the hybrid graphics mode. This is the most annoying problem and have forced me to use the hybrid graphics mode which I don't like. My first thought was either a specific NVIDIA issue or xorg misconfigurations. So I tried adding "acpi_backlight=vendor" and "nvdia.NVreg_RegistryDwords=EnableBrightnessControl=1" to GRUB, but didn't work at all. --- In discrete graphics mode, a quick "sudo journalctl -p3 -b0" showed below: Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: integrity: Problem loading X.509 certificate -65 Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20210730/psargs-330) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20210730/psparse-529) In hybrid graphics mode, "sudo journalctl -p3 -b0" output like above except that there was no: Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20210730/psargs-330) Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method \_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX Open Kernel Module for x86_64 520.56.06 Release Build (dvs-builder@U16-T12-10-2) Thu Oct 6 21:33:54 UTC 2022 GCC version: gcc
[Kernel-packages] [Bug 1993532] Re: Unable to see second monitor
When the bug resurfaced, was it still specific to the newer kernels? ** Summary changed: - Unable to see second monitor + Unable to see second monitor in 5.15.0-52 (but 5.15.0-50 works) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: i915 ** Summary changed: - Unable to see second monitor in 5.15.0-52 (but 5.15.0-50 works) + [i915] Unable to see second monitor in 5.15.0-52 (but 5.15.0-50 works) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993532 Title: [i915] Unable to see second monitor in 5.15.0-52 (but 5.15.0-50 works) Status in linux package in Ubuntu: Incomplete Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002314] Re: nouveau 0000:59:00.0: timeout in nvkm_falcon_v1_wait_for_halt
Comment #3 is an Intel driver issue so should be reported in a separate bug. -- 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/2002314 Title: nouveau :59:00.0: timeout in nvkm_falcon_v1_wait_for_halt Status in linux package in Ubuntu: Confirmed Bug description: This is a Hybrid graphics laptop with Ubuntu 22.10 (also happened with 22.04) and xserver-xorg-video-nouveau version 1.0.17-2build1. After locking the screen manually or automatically after the specified timeout, the whole laptop freeze or behave extremely slow, either ways a hard reset is a must by holding the power button to bring it back to life. This can happen right after the locking or after a while, but it doesn't happen if I suspended the laptop and wake it up. This doesn't happen if the nvidia proprietary driver is used. Right after a fresh boot, you can see the nouveau error in the attached dmesg.txt file. Sometimes while trying to unlock or switching to tty it shows such errors: 4010.649752) rcus INFO: rcu preempt detected stalls on CPUs/tasks: 4010.649766) rcus $0-...1: (1 GPs behind) idle-a58/0/0x0 softirq=30921/30922 fqs=0 (false positive?) 4010.649774) rout $2-... (0 ticks this GP) idle-4dc/0/0x0 softirq-26935/26935 fas-0 (false positive?) 4010.649776) rcut $3-...: (0 ticks this GP) idle-8ce/0/0x0 softirq-27111/27111 fqs=0 (false positive?) 4010.649777) rcus $4-...1: (1 GPs behind) idle-340/0/0x0 softirq-28041/28042 fqs=0 (false positive?) 4010.649779) rcus $6-...11 (0 ticks this GP) idle-86a/0/0x0 softirq-33526/33526 fas=0 (false positive?) 4010.649780) rous $7-... (1 GPs behind) idle=c01/1/0x4000 softirq-29455/29456 fqs=0 3115.864965) watchdog: BUG: soft lockup CPU#4 stuck for 515s! [Timer:5288) 3115.864972) 1915 :00:02.0: [drm] ERROR [CRTC:98:pipe A) filp.done timed out 3115.865030) watchdog: BUG: soft lockup- CPUW7 stuck for 515s! [Socket Thread:4856] 3115.865034) watchdog: BUG: soft lockup CPUW2 stuck for 515s! [snapd:5977) 3115.865046) watchdog: BUG: soft lockup- CPUW3 stuck for 515s! (openvpn:4633] 3115.865080) watchdog: BUG: soft lockup- CPU#6 stuck for $15s! [HebExtensions:5140) And: [2639.153118] NMI watchdog: Watchdog detected hard LOCKUP on cpu 7 [2661.862757] NHI watchdog: Watchdog detected hard LOCKUP on cpu 0 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 9 15:59:37 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-26-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1e6f] Subsystem: ASUSTeK Computer Inc. TU117M [GeForce MX450] [1043:1e6f] InstallationDate: Installed on 2023-01-04 (4 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Kernel-packages] [Bug 1997946] Re: [SRU] Support soundwire speaker AMP-ALC1318 codec
Install alsa-ucm-conf version 1.2.6.3-1ubuntu3 on MYBY- DVT1-C5_202212-31006 with 6.1.0-1004-oem kernel. Speaker works fine. ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1997946 Title: [SRU] Support soundwire speaker AMP-ALC1318 codec Status in OEM Priority Project: Triaged Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Bug description: [ Impact ] * Add ALC1318 speaker codec ucm file * Make internal speaker working on the platform with the codec [ Test Plan ] * On platform with the codec, the internal speaker should work after boot into Ubuntu [ Where problems could occur ] * The config only be executed on the platform with the codec exported * It needs to add the codec combination to the machine driver to make the function work ex. https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/intel/common/soc-acpi-intel-rpl-match.c#L225 [ Other Info ] * Upstream commit soundwire speaker AMP-ALC1318 codec. https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1997946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993532] 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/1993532 Title: Unable to see second monitor Status in linux package in Ubuntu: Confirmed Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993532] Re: Unable to see second monitor
** Changed in: linux (Ubuntu) Status: Expired => 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/1993532 Title: Unable to see second monitor Status in linux package in Ubuntu: New Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000465] Re: [SRU]rt715-sdca codec cannot record audio with internal microphone
Install alsa-ucm-conf version 1.2.6.3-1ubuntu3 on TRBR- DVT1-C4_202211-30860 with kernel 6.0.0-1009-oem. Follow the test steps and internal microphone works fine. ** Tags removed: verification-needed verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000465 Title: [SRU]rt715-sdca codec cannot record audio with internal microphone Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Bug description: [Impact] rt715-sdca codec cannot record audio with internal microphone [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Internal microphone should work propoerly. [Where problems could occur] Only fix for DUT with rt715-sdca device [Other Info] Upstream bug: https://github.com/alsa-project/alsa-ucm-conf/issues/255 Fix: https://github.com/alsa-project/alsa-ucm-conf/commit/e395d7b743584cba60876b6356fb3bc7834992aa To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997946] Re: [SRU] Support soundwire speaker AMP-ALC1318 codec
Install alsa-ucm-conf version 1.2.6.3-1ubuntu1.2 on MYBY- DVT1-C5_202212-31006 with 6.1.0-1004-oem kernel. Speaker works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1997946 Title: [SRU] Support soundwire speaker AMP-ALC1318 codec Status in OEM Priority Project: Triaged Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Bug description: [ Impact ] * Add ALC1318 speaker codec ucm file * Make internal speaker working on the platform with the codec [ Test Plan ] * On platform with the codec, the internal speaker should work after boot into Ubuntu [ Where problems could occur ] * The config only be executed on the platform with the codec exported * It needs to add the codec combination to the machine driver to make the function work ex. https://github.com/thesofproject/linux/blob/topic/sof-dev/sound/soc/intel/common/soc-acpi-intel-rpl-match.c#L225 [ Other Info ] * Upstream commit soundwire speaker AMP-ALC1318 codec. https://github.com/alsa-project/alsa-ucm-conf/commit/c82c400fb653292bbf0570e278d60e1ba14cc341 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1997946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000465] Re: [SRU]rt715-sdca codec cannot record audio with internal microphone
Install alsa-ucm-conf version 1.2.6.3-1ubuntu1.2 on TRBR- DVT1-C4_202211-30860 with kernel 6.0.0-1009-oem. Follow the test steps and internal microphone works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000465 Title: [SRU]rt715-sdca codec cannot record audio with internal microphone Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Kinetic: Fix Committed Bug description: [Impact] rt715-sdca codec cannot record audio with internal microphone [Test Plan] 1. stop alsa-restore service, "sudo systemctl stop alsa-restore.service" 2. remove old alsa status, "sudo rm /var/lib/alsa/asound.state" 3. reboot system 4. Internal microphone should work propoerly. [Where problems could occur] Only fix for DUT with rt715-sdca device [Other Info] Upstream bug: https://github.com/alsa-project/alsa-ucm-conf/issues/255 Fix: https://github.com/alsa-project/alsa-ucm-conf/commit/e395d7b743584cba60876b6356fb3bc7834992aa To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2000465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002385] Re: Memory error while booting
Downgrading to nvidia-driver-515 solved this issue for me. -- 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/2002385 Title: Memory error while booting Status in linux package in Ubuntu: Confirmed Bug description: I just installed ¨LinuxMint Vera Xfce" again after getting probably the same problem with an Ubuntu intstallation (ubuntu-22.04.1-desktop- amd64.iso) I tried out to get an external HDMI/VDI monitor working on my laptop. All worked fine with the default "Nouveau" video driver installed. I tried some xandr settings to check my external HDMI monitor, which basically worked. Then I noticed only the Nouveau driver was installed. I upgraded to the official (recommended by LinuxMint) NVidia-driver-525, did the compulsary reboot and got stuck with an "out of memory error" during that reboot (I don´t recall the literal message but something like that it was). The only option I had (because the install-USB oviously came with it) was choosing to boot with the previous 5.15.0-56 kernel which to my relief worked. After this boot I reverted to the Nouveau video driver and installed Kernel 5.15.0-57 again. So far this works, but I dare not install the official NVidia-driver-525 again. I don´t know if this is important, but so far I have no /etc/X11/xorg.conf file in place. I'm still trying to find out what a working configuration for my laptop with a secondary external IIyama screen is. I have an Acer Nitro VN7 with 12GB of internal memory, new 240 GB SSD boot drive and 1TB extra SATA HDD. Booting is setup for EFI (which is also far from fully developed it seems) with secure boot disabled. b.t.w. It seems I cannot add more than one attachment to this report. Version log is: Ubuntu 5.15.0-57.63-generic 5.15.74 1) lsb_release -rd: Description: Linux Mint 21.1 Release:21.1 2) n.a. 3) I expected to happen: flawless reboot 4) What happened instead: boot got stuck on a out of memory error. Extra info: default-display-manager (file in /etc/X11/): /usr/sbin/lightdm --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scutec 3996 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-09 (0 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: Acer Aspire VN7-792G NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=fc2964e7-baed-4419-a709-e3fb79bc9e17 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: vera Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2016 dmi.bios.release: 1.9 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd05/17/2016:br1.9:efr1.5:svnAcer:pnAspireVN7-792G:pvrV1.09:rvnAcer:rnAspireVN7-792G:rvrV1.09:cvnAcer:ct10:cvrV1.09:skuAspireVN7-792G_103B_1.09: dmi.product.family: SKL dmi.product.name: Aspire VN7-792G dmi.product.sku: Aspire VN7-792G_103B_1.09 dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002385] Re: Memory error while booting
I am experiencing the same thing with 5.15.0-57 and now 5.15.0-58. I also installed nvidia 525. My boot error gives the same out of memory error and then the kernel panic says ``` Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002385 Title: Memory error while booting Status in linux package in Ubuntu: Confirmed Bug description: I just installed ¨LinuxMint Vera Xfce" again after getting probably the same problem with an Ubuntu intstallation (ubuntu-22.04.1-desktop- amd64.iso) I tried out to get an external HDMI/VDI monitor working on my laptop. All worked fine with the default "Nouveau" video driver installed. I tried some xandr settings to check my external HDMI monitor, which basically worked. Then I noticed only the Nouveau driver was installed. I upgraded to the official (recommended by LinuxMint) NVidia-driver-525, did the compulsary reboot and got stuck with an "out of memory error" during that reboot (I don´t recall the literal message but something like that it was). The only option I had (because the install-USB oviously came with it) was choosing to boot with the previous 5.15.0-56 kernel which to my relief worked. After this boot I reverted to the Nouveau video driver and installed Kernel 5.15.0-57 again. So far this works, but I dare not install the official NVidia-driver-525 again. I don´t know if this is important, but so far I have no /etc/X11/xorg.conf file in place. I'm still trying to find out what a working configuration for my laptop with a secondary external IIyama screen is. I have an Acer Nitro VN7 with 12GB of internal memory, new 240 GB SSD boot drive and 1TB extra SATA HDD. Booting is setup for EFI (which is also far from fully developed it seems) with secure boot disabled. b.t.w. It seems I cannot add more than one attachment to this report. Version log is: Ubuntu 5.15.0-57.63-generic 5.15.74 1) lsb_release -rd: Description: Linux Mint 21.1 Release:21.1 2) n.a. 3) I expected to happen: flawless reboot 4) What happened instead: boot got stuck on a out of memory error. Extra info: default-display-manager (file in /etc/X11/): /usr/sbin/lightdm --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scutec 3996 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-09 (0 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: Acer Aspire VN7-792G NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-57-generic root=UUID=fc2964e7-baed-4419-a709-e3fb79bc9e17 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: vera Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/17/2016 dmi.bios.release: 1.9 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd05/17/2016:br1.9:efr1.5:svnAcer:pnAspireVN7-792G:pvrV1.09:rvnAcer:rnAspireVN7-792G:rvrV1.09:cvnAcer:ct10:cvrV1.09:skuAspireVN7-792G_103B_1.09: dmi.product.family: SKL dmi.product.name: Aspire VN7-792G dmi.product.sku: Aspire VN7-792G_103B_1.09 dmi.product.version: V1.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hi guys, I want to share my success story: It happened after I've updated to CUDA repo's nvidia drivers :) my `initrd.img-5.15.0-58-generic` (`ls -lah /boot`) was about 192M and using tuning option of the `/etc/initramfs-tools/initramfs.conf` file I've decreased it (`sudo update-initramfs -c -k 5.15.0-58-generic`) to 116M and now it works =) my `/etc/initramfs-tools/initramfs.conf` ``` # # initramfs.conf # Configuration file for mkinitramfs(8). See initramfs.conf(5). # # Note that configuration options from this file can be overridden # by config files in the /etc/initramfs-tools/conf.d directory. # # MODULES: [ most | netboot | dep | list ] # # most - Add most filesystem and all harddrive drivers. # # dep - Try and guess which modules to load. # # netboot - Add the base modules, network modules, but skip block devices. # # list - Only include modules from the 'additional modules' list # # original #MODULES=most # patch MODULES=dep # # BUSYBOX: [ y | n | auto ] # # Use busybox shell and utilities. If set to n, klibc utilities will be used. # If set to auto (or unset), busybox will be used if installed and klibc will # be used otherwise. # BUSYBOX=auto # # COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz | zstd ] # # original # COMPRESS=zstd COMPRESS=xz # # DEVICE: ... # # Specify a specific network interface, like eth0 # Overridden by optional ip= or BOOTIF= bootarg # DEVICE= # # NFSROOT: [ auto | HOST:MOUNT ] # NFSROOT=auto # # RUNSIZE: ... # # The size of the /run tmpfs mount point, like 256M or 10% # Overridden by optional initramfs.runsize= bootarg # RUNSIZE=10% # # FSTYPE: ... # # The filesystem type(s) to support, or "auto" to use the current root # filesystem type # FSTYPE=auto # patch export XZ_OPT='--lzma2=preset=0,dict=8M' ``` Hope it will help you (and don't forget about `sudo update-initramfs -c -k YOUR_VERSION-generic`). Keep yourself safe (from kernel panics too) and Glory to Ukraine! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Fix Committed Status in grub2-unsigned package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory region starvation in <1G addresses: Type StartEnd # Pages Attributes Available -00086FFF 0087 000F BS_Data00087000-00087FFF 0001 000F Available 00088000-0009EFFF 0017 000F Reserved 0009F000-0009 0001 000F Available 0010-00FF 0F00 000F LoaderCode 0100-01021FFF 0022 000F Available 01022000-238A7FFF 00022886 000F BS_Data238A8000-23927FFF 0080 000F Available 23928000-28860FFF 4F39 000F BS_Data28861000-2AB09FFF 22A9 000F LoaderCode 2AB0A000-2ACF8FFF 01EF 000F BS_Data2ACF9000-2B2FAFFF
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
Log 9.4: shutdown debbuged system via ssh ** Attachment added: "netconsole.log-9.4-shutdown" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641506/+files/netconsole.log-9.4-shutdown -- 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/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
Log 9.3: ssh into debugged system ** Attachment added: "netconsole.log-9.3-ssh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641505/+files/netconsole.log-9.3-ssh -- 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/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
Log 9.2: open terminal and issue sudo systemctl suspend ** Attachment added: "netconsole.log-9.2-terminal-suspend" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641504/+files/netconsole.log-9.2-terminal-suspend -- 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/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
Log 9.1: bootup into desktop with nomodeset ** Attachment added: "netconsole.log-9.1-boot-up" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641503/+files/netconsole.log-9.1-boot-up -- 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/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
Log 8: Shutting down - opening terminal and issuing: sudo shutdown now ** Attachment added: "netconsole.log-8-shutting-down-from-terminal" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641502/+files/netconsole.log-8-shutting-down-from-terminal -- 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/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
Log 8: Booting up the system into the desktop (user logged in automatically) - with nomodeset. ** Attachment added: "netconsole.log-8-clean-boot-into-the-desktop" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641501/+files/netconsole.log-8-clean-boot-into-the-desktop -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
I've confirmed that 6.1.0-1004-oem (the current version of linux-image- oem-22.04c) does not have the screen disabling bug. I'll test for stability in the face of amdgpu protection faults today and see what happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Incomplete Bug description: When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
NOTE: by using nomodeset for kernel boot option, the system boots fine and runs fine. Only issue is when it is sent to sleep and has to wake up! Attached a netconsole log for the below scenario: booted with nomodeset started firefox loaded google.com closed firefox CTRL+ALT+T to start a terminal window started a 2nd terminal window waited and did nothing for about 1 minute issued sudo systemctl suspend in about 1 minutes time I pressed the power button to wake up the system then SSH into the system ran top, all went fine ** Attachment added: "netconsole.log-5-with-nomodeset-sent-to-sleep-and-woken-up" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641500/+files/netconsole.log-5-with-nomodeset-sent-to-sleep-and-woken-up -- 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/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]
I had a crash with 5.19.0-28-generic as well -- 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/1585434 Title: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Status in linux package in Ubuntu: Confirmed Bug description: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] ecryptfs_readpage: Error decrypting page; rc = [-4] I dont' have this issue showing in dmesg when using 3.19 kernel, only with later kernels. Is it related to selecting encrypted home on install or something? I don't notice any issues with performance because of it or have any other error messages. I am using default ubuntu xenial 16.04 with unity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cooloutac 2054 F pulseaudio /dev/snd/pcmC0D0p: cooloutac 2054 F...m pulseaudio /dev/snd/controlC0: cooloutac 2054 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 22:38:44 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1 InstallationDate: Installed on 2016-05-20 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0NWWY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 7100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
netconsole.log-4-frozen-after-about-50-seconds-after-desktop-shown- without-nomodeset (has some CPU not responding at the end) NOTE: netconsole is very nice! :) on the host machine (the one that is being debugged), for me wifi was not suitable and had to switch to eth (cable) in order for this to work. For anyone willing to do similar debugging the below link might be helpful: https://wiki.ubuntu.com/DebuggingKernelBoot ** Attachment added: "netconsole.log-4-frozen-after-about-50-seconds-after-desktop-shown-without-nomodeset" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641499/+files/netconsole.log-4-frozen-after-about-50-seconds-after-desktop-shown-without-nomodeset -- 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/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
netconsole.log-3-frozen-after-desktop-shown-less-than-20-seconds- without-nomodeset ** Attachment added: "netconsole.log-3-frozen-after-desktop-shown-less-than-20-seconds-without-nomodeset" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641498/+files/netconsole.log-3-frozen-after-desktop-shown-less-than-20-seconds-without-nomodeset -- 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/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
netconsole.log-2-frozen-after-aprox-25-seconds-after-desktop-without- nomodeset (has some CPU not responding at the end) ** Attachment added: "netconsole.log-2-frozen-after-aprox-25-seconds-after-desktop-without-nomodeset" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641497/+files/netconsole.log-2-frozen-after-aprox-25-seconds-after-desktop-without-nomodeset -- 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/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
With the help of tomreyn (Tom Reynolds) from #ubuntu on libera.chat I managed to gather the attached netconsole kernel debug info. The no 2 and no 4 contain at the very end a CPU not responding and shutting down CPUs. This is on a fresh install of 22.10 with no updates (only some other installs like netconsole, mc, etc). If there is any more I can provide, feel free to comment. netconsole.log.1-frozen-2-seconds-after-desktop-shows-without-nomodeset ** Attachment added: "netconsole.log.1-frozen-2-seconds-after-desktop-shows-without-nomodeset" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641496/+files/netconsole.log.1-frozen-2-seconds-after-desktop-shows-without-nomodeset -- 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/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@kolbjorn could you please provide the output of `lsusb -v -d 0408:4033` (running as root, for instance with sudo, if possible) ? Attaching a file would be preferred to avoid messing up formatting. -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ignis_ADH
[Kernel-packages] [Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]
I am seeing this in Ubuntu 22.10 5.19.0-30-generic. I booted into 5.19.0-28-generic to see if I see the same with this kernel version. -- 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/1585434 Title: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] Status in linux package in Ubuntu: Confirmed Bug description: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4] ecryptfs_readpage: Error decrypting page; rc = [-4] I dont' have this issue showing in dmesg when using 3.19 kernel, only with later kernels. Is it related to selecting encrypted home on install or something? I don't notice any issues with performance because of it or have any other error messages. I am using default ubuntu xenial 16.04 with unity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cooloutac 2054 F pulseaudio /dev/snd/pcmC0D0p: cooloutac 2054 F...m pulseaudio /dev/snd/controlC0: cooloutac 2054 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 22:38:44 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1 InstallationDate: Installed on 2016-05-20 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Studio XPS 7100 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0NWWY0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: Studio XPS 7100 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002834] Re: Network bridge issue after updating kernel to 5.4.0-137
Exact same issue here with jammy and going from 5.15.0-57.63 to 5.15.0-58.64 the issue is also reproduced with 5.15.0.59.57 (proposed) Context is xen host, bond + vlans + bridge for xen VMs Network is ok on the host, VM are not working, very weird, you can see some traffic coming through the bridge to the VM, but not on the other way around. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2002834 Title: Network bridge issue after updating kernel to 5.4.0-137 Status in linux-meta package in Ubuntu: Confirmed Bug description: Hello, After updating the kernel from 5.4.0-136 to 5.4.0-137 network bridge are not working any more. I can see the bridge with "ip add show" or "brctl show". Network is up and I can reach the full network from the host through the bridge. VM on the host can not reach network or host and host can not reach the VM through the bridge. We have bonded interface used in the bridge and one bridge without IP and one with an IP. DHCP is off on booth bridge. Downgrading the kernel to 5.4.136 (Ubuntu 5.4.0-136.153-generic 5.4.218) seem to work fine. Thank you for your help. Details Description: Ubuntu 20.04.5 LTS Release: 20.04 Not working version => Ubuntu 5.4.0-137.154-generic 5.4.218 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2002834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002834] Re: Network bridge issue after updating kernel to 5.4.0-137
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2002834 Title: Network bridge issue after updating kernel to 5.4.0-137 Status in linux-meta package in Ubuntu: Confirmed Bug description: Hello, After updating the kernel from 5.4.0-136 to 5.4.0-137 network bridge are not working any more. I can see the bridge with "ip add show" or "brctl show". Network is up and I can reach the full network from the host through the bridge. VM on the host can not reach network or host and host can not reach the VM through the bridge. We have bonded interface used in the bridge and one bridge without IP and one with an IP. DHCP is off on booth bridge. Downgrading the kernel to 5.4.136 (Ubuntu 5.4.0-136.153-generic 5.4.218) seem to work fine. Thank you for your help. Details Description: Ubuntu 20.04.5 LTS Release: 20.04 Not working version => Ubuntu 5.4.0-137.154-generic 5.4.218 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2002834/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996071] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2023-01-15 11:13 EDT--- Fix is now available in focal, jammy and kinetic, therefore we can close this bug. Thanks everyone for your work! ==> Changing the status to: CLOSED -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996071 Title: [UBUNTU 20.04] boot: Add s390x secure boot trailer Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: == [Impact] * Secure boot of Linux on s390x will no longer be possible with an upcoming IBM zSystems firmware update. [Fix] * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure boot trailer" for kinetic and jammy * https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch backport for focal [Test Plan] * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is required. * Ensure that 'Enable Secure Boot for Linux' is marked in case 'SCSI Load' is selected at the HMCs Load task and Activation Profile. * Perform an Ubuntu Server installation, either 20.04 or 22.04 (latest ISO). It will be a secure boot installation by default in case 'Enable Secure Boot for Linux' was marked. * Check sysfs: /sys/firmware/ipl/has_secure '1' indicates hw support for secure boot, otherwise '0' /sys/firmware/ipl/secure '1' indicates that secure IPL was successful, otherwise '0' * Navigate to the HMC task 'System information' and check the active firmware release. * Ensure that Ubuntu is still bootable in secure-boot mode with the updated firmware active, by for example doing a reboot after the firmware upgrade. * There is also a way to test the trailer on systems that do not have the updated firmware yet - in this case use the following script: https://launchpadlibrarian.net/633126861/check_sb_trailer.sh [Where problems could occur] * The 'trailer' might be broken, invalid or in a wrong format and can't be identified or read properly, or may cause issues while compressing/decompressing the kernel. * In worst case secure boot might become broken, even on systems that are still on the unpatched firmware level. * Or secure boot will become broken in general. [Other Info] * The above commit was upstream accepted with v6.1-rc3. * And it got tagged for upstream stable with: "Cc: # 5.2+" * But since this bug is marked as critical, and the patch is relatively short, traceable and s390x-specific, I'll go ahead and submit this patch for Jammy and Focal ahead of upstream stable. * Since on focal file 'vmlinux.lds.S' is at a different location 'arch/s390/boot/compressed/' instead of 'arch/s390/boot/' and the context is slightly different, the backport is needed. * It's planned to have kernel 6.2 in lunar (23.04), hence it will have the patch incl. when at the planned target level. __ Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000829] Re: Ubuntu 22.10 only works with nomodeset - will freeze otherwise
I have freshly reinstalled 22.10 from USB live with nomodeset added at boot in GRUB. Then, after install I issued: sudo systemctl suspend The system went into suspend mode. After, I woke up the system by pressing the power button. The screen remained blank, however, I have noticed the keyboard backlight to switch on and then fade away and switch back on if I moved around on the touchpad. Therefore, I have tried to log in as usual (without seeing anything), after which I pressed CTRL+ALT+T to launch a terminal and then I used: sudo reboot Followed by my password. And the system rebooted. Then, even further, I have managed to SSH to this Dell Latitude 7390 and can now confirm, the system is fine after wake up, with the screen remaining blank/black. I have attached the output for: journalctl -eb -1 Which contains the wake-up process. ** Attachment added: "journalctl" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+attachment/5641449/+files/log2 -- 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/2000829 Title: Ubuntu 22.10 only works with nomodeset - will freeze otherwise Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 only works with nomodeset - will freeze otherwise. A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point. After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly. Further, if I issue the command in the retminal: systemctl suspend or systemctl hibernate The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again. I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up. I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up? NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-26-generic 5.19.0-26.27 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximus1481 F wireplumber /dev/snd/seq:maximus1478 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 1 11:14:34 2023 InstallationDate: Installed on 2023-01-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7390 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-26-generic N/A linux-backports-modules-5.19.0-26-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.30.0 dmi.board.name: 09386V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B: dmi.product.family: Latitude dmi.product.name: Latitude 7390 dmi.product.sku: 081B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 2002894] 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 2002894 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/2002894 Title: ACPI error startup after upgrade to Ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: See attached screenshot of ACPI error messages on start up since upgrade to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002894] Re: ACPI error startup after upgrade to Ubuntu 22.04.1 LTS
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002894 Title: ACPI error startup after upgrade to Ubuntu 22.04.1 LTS Status in linux package in Ubuntu: New Bug description: See attached screenshot of ACPI error messages on start up since upgrade to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002894] [NEW] ACPI error startup after upgrade to Ubuntu 22.04.1 LTS
You have been subscribed to a public bug: See attached screenshot of ACPI error messages on start up since upgrade to 22.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- ACPI error startup after upgrade to Ubuntu 22.04.1 LTS https://bugs.launchpad.net/bugs/2002894 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp