[Kernel-packages] [Bug 2046504] Re: AMD GPU display is blank when set lower resolution than native mode on eDP
** Changed in: linux Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: AMD GPU display is blank when set lower resolution than native mode on eDP Status in HWE Next: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes are set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727861] Re: kernel BUG at /build/linux-hwe-IJy1zi/linux-hwe-4.10.0/fs/cachefiles/namei.c:164!
** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1727861 Title: kernel BUG at /build/linux-hwe-IJy1zi/linux- hwe-4.10.0/fs/cachefiles/namei.c:164! Status in Linux: Confirmed Status in linux-meta-hwe package in Ubuntu: Fix Committed Status in cachefilesd package in Debian: Fix Released Bug description: I have just installed cachefilesd and rebooted. The only change I made was the location of the cache - everything else is set to default. The cache location exists and is writable. I thought I'd test so first attempt: $ cat /mnt/server/share/file > /dev/null No problem. Second attempt: $ cat /mnt/server/share/file > /dev/null [ 471.283546] [ cut here ] [ 471.288354] kernel BUG at /build/linux-hwe-IJy1zi/linux-hwe-4.10.0/fs/cachefiles/namei.c:164! [ 471.296977] invalid opcode: [#1] SMP [ 471.301172] Modules linked in: arc4 md4 cachefiles cifs ccm fscache ip6table_filter ip6_tables iptable_filter ip_tables x_tables ppdev pvpanic input_leds parport_pc serio_raw parport autofs4 btrfs xor raid6_pq crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_net virtio_scsi [ 471.332032] CPU: 0 PID: 5 Comm: kworker/u2:0 Not tainted 4.10.0-37-generic #41~16.04.1-Ubuntu [ 471.340656] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 [ 471.350158] Workqueue: fscache_object fscache_object_work_func [fscache] [ 471.356972] task: 8ddee426ad00 task.stack: bb3f401b [ 471.363083] RIP: 0010:cachefiles_walk_to_object+0x718/0x890 [cachefiles] [ 471.370055] RSP: 0018:bb3f401b3d18 EFLAGS: 00010202 [ 471.375385] RAX: 8ddee18a6201 RBX: 8ddee0b6bd28 RCX: 00019523 [ 471.382897] RDX: 00019522 RSI: 8ddee621c720 RDI: 8ddee4001280 [ 471.390234] RBP: bb3f401b3dc8 R08: 0001c720 R09: c0459068 [ 471.397468] R10: e66040862980 R11: 97c487ed R12: 8ddee11750c0 [ 471.404704] R13: 8ddee0b6bd80 R14: 8ddee0b6bd28 R15: 8ddee1175780 [ 471.411991] FS: () GS:8ddee620() knlGS: [ 471.420180] CS: 0010 DS: ES: CR0: 80050033 [ 471.426037] CR2: 025c4008 CR3: 20b6a000 CR4: 001406f0 [ 471.433359] DR0: DR1: DR2: [ 471.440678] DR3: DR6: fffe0ff0 DR7: 0400 [ 471.447921] Call Trace: [ 471.450478] ? wake_atomic_t_function+0x60/0x60 [ 471.455109] cachefiles_lookup_object+0x51/0xf0 [cachefiles] [ 471.460872] fscache_look_up_object+0xa6/0x1c0 [fscache] [ 471.466378] fscache_object_work_func+0x9d/0x200 [fscache] [ 471.472012] process_one_work+0x16b/0x4a0 [ 471.476118] worker_thread+0x4b/0x500 [ 471.479880] kthread+0x109/0x140 [ 471.483294] ? process_one_work+0x4a0/0x4a0 [ 471.487577] ? kthread_create_on_node+0x60/0x60 [ 471.492208] ret_from_fork+0x2c/0x40 [ 471.495879] Code: 78 ff ff ff 4c 89 f7 49 89 de 48 8b 00 ff 50 58 e9 b5 fc ff ff 48 c7 c7 68 b3 45 c0 e8 b5 75 75 d6 31 f6 4c 89 ef e8 bd 2c 00 00 <0f> 0b 41 bc ff ff ff ff 48 8b 90 98 00 00 00 48 8b bd 78 ff ff [ 471.514854] RIP: cachefiles_walk_to_object+0x718/0x890 [cachefiles] RSP: bb3f401b3d18 [ 471.523171] ---[ end trace d57820f35931610a ]--- I tried with the following builds but the result is the same: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.17/linux-image-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc6/linux-image-4.14.0-041400rc6-generic_4.14.0-041400rc6.201710230731_amd64.deb I tried setting the cache back to the default of /var/cache/fscache and it seemed to start working. I ran the test three or four times. Then it failed in the same way. I'm running Ubuntu 16.04 on Google Cloud Compute. In case it's a filesystem issue: $ sudo dumpe2fs -h /dev/sda1 dumpe2fs 1.42.13 (17-May-2015) Filesystem volume name: cloudimg-rootfs Last mounted on: / Filesystem UUID: 67e1c0a6-cdc9-4247-b2e5-dd20ef042025 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options:user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 128 Block count: 2621179 Reserved block count: 0 Free blocks: 1076375
[Kernel-packages] [Bug 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
We would run into auto reboot issue during suspend test with linux- firmware package in proposed kernel. Qualcomm is working on fixing this through upstream firmware update. -- 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/2048977 Title: WCN6856 Wi-FI Unavailable and no function during suspend stress Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: In Progress Bug description: [SRU Justification] [Impact] Due to a known silicon limitation, the following sequence is needed while initialing the PCIE device on a certain devices with ASMedia chipset involved: 1. 'hot reset' assert 2. 2nd PCIe reset' assert 3. Asmedia 'hot reset' deassert 4. PT21 GPIO13 2nd PCIe reset' deassert. In certain caes, the WIFI link training failed while system resumes from suspend. [Fix] Upstream commits: * 17509e53b97b ("ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36") * 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin") And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0: update board-2.bin") to forfill git history dependency. And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble has not yet accept the PR for bug 2042534, it has no such problem at this moment. [Test Case] This can be reproduced with suspend/resume stress test. $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Opaque firmware update. No known issue found yet after the update. [Other Info] This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and Jammy for oem-6.5 included. == original bug report == Due to a known silicon limitation, the following sequence is needed while initialing the PCIE device on a certain devices with ASMedia chipset involved: 1. 'hot reset' assert 2. 2nd PCIe reset' assert 3. Asmedia 'hot reset' deassert 4. PT21 GPIO13 2nd PCIe reset' deassert. In certain caes, the WIFI link training failed while system resumes from suspend. This can be reproduced with suspend/resume stress test. $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated The proposed fixes are: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199 - This FW include this LP ticket issue fix * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe - The FW is to support new China regulatory support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2048977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
Hello! Any news about this issue? I have the same problem on a freshly installed kubuntu 22.04.3 LTS on a ASUS laptop with AMD Ryzen 9 7845HX and RTX 4060 GPU. Disabling the module xhci_pci works, but unfortunately in my case when I do this the keyboard becomes completely inactive. Is there a way to blacklist this module without disabling the keyboard? -- 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/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework
[Kernel-packages] [Bug 2051292] Re: [BCM43142] Bluetooth headset disconnects
It looks like there are Bluetooth packet problems at the kernel level (if not hardware), so reassigning there. ** Summary changed: - blutooth + [BCM43142] Bluetooth headset disconnects ** Package changed: bluez (Ubuntu) => linux-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051292 Title: [BCM43142] Bluetooth headset disconnects Status in linux-hwe-6.5 package in Ubuntu: New Bug description: when I connect to my headset it's work couple of seconds or minutes then disconnect alone ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 22:15:26 2024 InstallationDate: Installed on 2023-06-27 (211 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: btusb rfcomm bnep bluetooth MachineType: Dell Inc. Inspiron 3721 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=4d42ff5a-4c75-44c8-a459-6df10d860db0 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 044D20 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/29/2013:efr1.1:svnDellInc.:pnInspiron3721:pvrA11:rvnDellInc.:rn044D20:rvrA00:cvnDellInc.:ct8:cvrA11:skuInspiron3721: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3721 dmi.product.sku: Inspiron 3721 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:2A:70:BE:D0:62 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:5227 acl:60 sco:0 events:440 errors:0 TX bytes:36549 acl:67 sco:0 commands:391 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046224] Re: [amdgpu] Resolutions lower than max results in corrupted screen
*** This bug is a duplicate of bug 2046504 *** https://bugs.launchpad.net/bugs/2046504 The fix was tracked in bug 2046504. ** This bug has been marked a duplicate of bug 2046504 AMD GPU display is blank when set lower resolution than native mode on eDP -- 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/2046224 Title: [amdgpu] Resolutions lower than max results in corrupted screen Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Upgrading from 23.04 to 23.10 resulted in corrupt screen when switching to lower resolutions. Only maximum resolution works. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 12 01:21:01 2023 DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading DistroCodename: mantic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Phoenix [17aa:3c92] InstallationDate: Installed on 2023-11-04 (38 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash amd_pstate=guided vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago) dmi.bios.date: 06/16/2023 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: M3CN34WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Slim 5 16APH8 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrM3CN34WW:bd06/16/2023:br1.34:efr1.34:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8: dmi.product.family: Legion Slim 5 16APH8 dmi.product.name: 82Y9 dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8 dmi.product.version: Legion Slim 5 16APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1 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 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2046224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046504] Re: AMD GPU display is blank when set lower resolution than native mode on eDP
** Summary changed: - Fix AMDGPU display on lower resolution modes + AMD GPU display is blank when set lower resolution than native mode on eDP ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2693 https://gitlab.freedesktop.org/drm/amd/-/issues/2693 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/2693 Importance: Unknown Status: Unknown ** Tags added: amdgpu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: AMD GPU display is blank when set lower resolution than native mode on eDP Status in HWE Next: Fix Released Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes are set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049976] Re: Analog VGA goes black on resume
** Package changed: linux (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049976 Title: Analog VGA goes black on resume Status in Ubuntu: Invalid Bug description: Starting a few weeks ago after applying regular maintenance to 22.04.3 LTS one of my two displays, an LG 22MP47HQ-P connected to my tower by a D-Sub cable, blinked multiple times immediately on resume from suspend. My second display which is connected using HDMI works normally. This, of course, was merely a mild annoyance because after a few seconds it stopped. However in the past week that same display flashes on, and then goes black. I power the display off and back on and again it flashes on for a fraction of a second and then goes black. After several power cycles of the display it stays on, so again this is only a mild annoyance. Is this a known issue with a recent update? Specifically this is after a deep suspend, one where on unlock you need to press a key to get the login prompt. I tried updating to 23.10 but the problem is there as well. This bug tool does not permit reporting a problem against Wayland. lshw -C video *-display description: VGA compatible controller product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 resolution=1920,1080 resources: irq:31 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) memory:c-d /var/log/apt/history.log taken immediately after encountering the issue on 22.04 Start-Date: 2024-01-02 16:01:30 Commandline: aptdaemon role='role-commit-packages' sender=':1.7295' Upgrade: thunderbird:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-gb:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-gnome-support:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1) End-Date: 2024-01-02 16:01:33 Start-Date: 2024-01-03 16:57:04 Commandline: /usr/bin/unattended-upgrade Upgrade: libsqlite3-dev:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), libsqlite3-0:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), sqlite3:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3) End-Date: 2024-01-03 16:57:05 Start-Date: 2024-01-03 16:57:08 Commandline: /usr/bin/unattended-upgrade Upgrade: openssh-client:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), openssh-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), openssh-sftp-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6) End-Date: 2024-01-03 16:57:10 Start-Date: 2024-01-03 16:57:13 Commandline: /usr/bin/unattended-upgrade Upgrade: libnode72:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), nodejs:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), libnode-dev:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3) End-Date: 2024-01-03 16:57:14 Start-Date: 2024-01-03 16:57:16 Commandline: /usr/bin/unattended-upgrade Upgrade: nodejs-doc:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3) End-Date: 2024-01-03 16:57:17 Start-Date: 2024-01-09 20:43:19 Commandline: aptdaemon role='role-commit-packages' sender=':1.9514' Install: php8.3-xml:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), php8.3-mbstring:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), php8.3-common:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), php8.3-intl:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic) Upgrade: php-common:amd64 (2:93+ubuntu22.04.1+deb.sury.org+3, 2:94+ubuntu22.04.1+deb.sury.org+1), software-properties-common:amd64 (0.99.22.8, 0.99.22.9), python3-software-properties:amd64 (0.99.22.8, 0.99.22.9), php-intl:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), php-mbstring:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), software-properties-gtk:amd64 (0.99.22.8, 0.99.22.9), python3-distro-info:amd64 (1.1ubuntu0.1, 1.1ubuntu0.2), distro-info-data:amd64 (0.52ubuntu0.5, 0.52ubuntu0.6), linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.23, 20220329.git681281e4-0ubuntu3.24), php-xml:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), distro-info:amd64 (1.1ubuntu0.1, 1.1ubuntu0.2) End-Date: 2024-01-09 20:45:50 Start-Date: 2024-01-10 21:58:10 Commandline: /usr/bin/unattended-upgrade Upgra
[Kernel-packages] [Bug 2042867] Re: Changing display resolution leads into black screen
*** This bug is a duplicate of bug 2046504 *** https://bugs.launchpad.net/bugs/2046504 ** This bug has been marked a duplicate of bug 2046504 AMD GPU display is blank when set lower resolution than native mode on eDP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042867 Title: Changing display resolution leads into black screen Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Confirmed Bug description: Since updating into 23.10, when I change my build-in display from 2880x1800 (16:10) at 90Hz to any other resolution, it turns the screen black and unable to use. The only resolution that works is the predefined one. This bug wasn't present on the previous release, 23.04. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-10-generic 6.5.0-10.10 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 6 19:37:48 2023 InstallationDate: Installed on 2023-05-05 (185 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv 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-6.5.0-10-generic N/A linux-backports-modules-6.5.0-10-generic N/A linux-firmware20230919.git3672ccab-0ubuntu2.1 SourcePackage: linux UpgradeStatus: Upgraded to mantic on 2023-11-03 (3 days ago) dmi.bios.date: 04/18/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM5401QAB_UM5401QA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM5401QAB 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.:bvrUM5401QAB_UM5401QA.302:bd04/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenbookUM5401QAB_UM5401QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5401QAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UM5401QAB_UM5401QA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2042867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043515] Re: Black screen on 6.5
*** This bug is a duplicate of bug 2046504 *** https://bugs.launchpad.net/bugs/2046504 ** This bug is no longer a duplicate of bug 2042867 Changing display resolution leads into black screen ** This bug has been marked a duplicate of bug 2046504 AMD GPU display is blank when set lower resolution than native mode on eDP -- 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/2043515 Title: Black screen on 6.5 Status in linux package in Ubuntu: New Bug description: Hello, the screen stays black under many resolutions on Ryzen on kernel 6.5. It worked well up until the update (from 6.2). It seems to be a known regression already fixed in upstream. Could you also apply the patch https://www.spinics.net/lists/stable/msg679132.html? Thank you. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-10-generic 6.5.0-10.10 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Nov 14 22:48:59 2023 InstallationDate: Installed on 2023-08-07 (99 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.5.0-10-generic N/A linux-backports-modules-6.5.0-10-generic N/A linux-firmware20230919.git3672ccab-0ubuntu2.1 SourcePackage: linux UpgradeStatus: Upgraded to mantic on 2023-11-03 (12 days ago) dmi.bios.date: 08/08/2023 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R22ET65W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CNS17C00 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 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.27 dmi.modalias: dmi:bvnLENOVO:bvrR22ET65W(1.35):bd08/08/2023:br1.35:efr1.27:svnLENOVO:pn21CNS17C00:pvrThinkPadX13Gen3:rvnLENOVO:rn21CNS17C00:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CN_BU_Think_FM_ThinkPadX13Gen3: dmi.product.family: ThinkPad X13 Gen 3 dmi.product.name: 21CNS17C00 dmi.product.sku: LENOVO_MT_21CN_BU_Think_FM_ThinkPad X13 Gen 3 dmi.product.version: ThinkPad X13 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Yes I believe 22.04 is the only supported release that has/had this bug. But we'd like to know what caused it there (and if it's still happening). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049317] Re: UBSAN array-index-out-of-bounds error in dmesg - amd gpu drivers
I've started seeing this for the Virtualbox modules. Could just be a coincidence but thought I'd mention it. ** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049317 Title: UBSAN array-index-out-of-bounds error in dmesg - amd gpu drivers Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: lsb_release -a System info Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy uname -a Linux dario-Aspire-E5-553G 6.5.0-14-generic #14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux At boot and in dmesg (and /var/log/syslog) this error appears, repeated multiple times, I don't remember seeing it in the past, If necessary I can provide the ful /var/log/syslog file: Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.503732] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.504707] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1502:42 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.506717] index 1 is out of range for type 'ATOM_PPLIB_CAC_Leakage_Record [1]' Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507673] CPU: 1 PID: 136 Comm: systemd-udevd Not tainted 6.5.0-14-generic #14~22.04.1-Ubuntu Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507677] Hardware name: Acer Aspire E5-553G/Wasp_BR, BIOS V1.31 03/28/2018 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507679] Call Trace: Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507681] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507684] dump_stack_lvl+0x48/0x70 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507694] dump_stack+0x10/0x20 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507696] __ubsan_handle_out_of_bounds+0xc6/0x110 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507701] init_dpm2_parameters+0x2d6/0x360 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.509001] pp_tables_initialize+0x12c/0x440 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.510250] ? amdgpu_ring_test_helper+0x83/0x90 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.511425] hwmgr_hw_init+0x7b/0x1e0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.512733] pp_hw_init+0x16/0x50 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.513987] amdgpu_device_ip_init+0x48d/0x960 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.515143] amdgpu_device_init+0x9c8/0x1160 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.516313] amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.517507] amdgpu_pci_probe+0x182/0x450 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518678] local_pci_probe+0x47/0xb0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518684] pci_call_probe+0x55/0x190 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518688] pci_device_probe+0x84/0x120 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518692] really_probe+0x1cc/0x430 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518696] __driver_probe_device+0x8c/0x190 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518709] driver_probe_device+0x24/0xd0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518712] __driver_attach+0x10b/0x210 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518715] ? __pfx___driver_attach+0x10/0x10 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518718] bus_for_each_dev+0x8d/0xf0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518723] driver_attach+0x1e/0x30 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518727] bus_add_driver+0x127/0x240 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518731] driver_register+0x5e/0x130 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518735] ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.519866] __pci_register_driver+0x62/0x70 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.519871] amdgpu_init+0x69/0xff0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521048] do_one_initcall+0x5e/0x340 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521056] do_init_module+0x68/0x260 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521062] load_module+0xb85/0xcd0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521066] ? security_kernel_post_read_file+0x75/0x90 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521070] ? security_kernel_post_read_file+0x75/0x90 Jan 14 20:24:13 dario-Aspire-E5-553G k
[Kernel-packages] [Bug 2051418] Re: Error in removing linux-image-6.5.0-14-generic
** Project changed: subiquity => ubuntu ** Package changed: ubuntu => linux-meta-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051418 Title: Error in removing linux-image-6.5.0-14-generic Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: Here is the error when trying to upgrade Ubuntu: $ sudo apt-get autoremove [sudo] password for minisforum-um790pro-nicolas: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: linux-image-6.5.0-14-generic 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 14.3 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 248924 files and directories currently installed.) Removing linux-image-6.5.0-14-generic (6.5.0-14.14) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-6.5.0-14-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' /usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not found run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127 dpkg: error processing package linux-image-6.5.0-14-generic (--remove): installed linux-image-6.5.0-14-generic package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: linux-image-6.5.0-14-generic Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.113.01-0ubuntu3_amd64.deb ./casper/minimal.standard.live.squashfs CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sat Jan 27 10:39:26 2024 InstallationDate: Installed on 2023-10-29 (90 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: subiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2051418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051418] [NEW] Error in removing linux-image-6.5.0-14-generic
You have been subscribed to a public bug: Here is the error when trying to upgrade Ubuntu: $ sudo apt-get autoremove [sudo] password for minisforum-um790pro-nicolas: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: linux-image-6.5.0-14-generic 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 14.3 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 248924 files and directories currently installed.) Removing linux-image-6.5.0-14-generic (6.5.0-14.14) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-6.5.0-14-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' /usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not found run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127 dpkg: error processing package linux-image-6.5.0-14-generic (--remove): installed linux-image-6.5.0-14-generic package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: linux-image-6.5.0-14-generic Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.113.01-0ubuntu3_amd64.deb ./casper/minimal.standard.live.squashfs CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sat Jan 27 10:39:26 2024 InstallationDate: Installed on 2023-10-29 (90 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: subiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ubuntu-desktop-installer wayland-session -- Error in removing linux-image-6.5.0-14-generic https://bugs.launchpad.net/bugs/2051418 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
This is a regression for jammy in the update of the linux-generic- hwe-22.04 package to version 6.5. So I guess that's more regression- update than regression-release. It won't be a regression-release unless the issue is still unresolved in 22.04.4. ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-450-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-470 source package in Jammy: Invalid Status in nvidia-graphics-drivers-470-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-525 source package in Jammy: Invalid Status in nvidia-graphics-drivers-525-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
This is occurring on the Kubuntu Focus NX Gen 2 as well. ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685 It was fixed with that kernel commit: commit 648d7be8ecf47b0556e32550145c70db153b16fb Author: Ville Syrjälä Date: Mon Dec 11 23:37:47 2023 +0200 drm/i915/dmc: Don't enable any pipe DMC events https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/ which was picked for 6.6.9. I'd like to ask whether it is possible to apply that patch to the current Ubuntu kernel? Best Sönke ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 11 13:11:59 2024 InstallationDate: Installed on 2023-03-01 (316 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049027] Re: The display becomes frozen after some time when a HDMI device is connected.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049027 Title: The display becomes frozen after some time when a HDMI device is connected. Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685 It was fixed with that kernel commit: commit 648d7be8ecf47b0556e32550145c70db153b16fb Author: Ville Syrjälä Date: Mon Dec 11 23:37:47 2023 +0200 drm/i915/dmc: Don't enable any pipe DMC events https://lore.kernel.org/stable/20231211213750.27109-2-ville.syrj...@linux.intel.com/ which was picked for 6.6.9. I'd like to ask whether it is possible to apply that patch to the current Ubuntu kernel? Best Sönke ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 11 13:11:59 2024 InstallationDate: Installed on 2023-03-01 (316 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051470] Re: Finding wifi is unstable in this release
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051470 Title: Finding wifi is unstable in this release Status in linux package in Ubuntu: New Bug description: After a recent upgrade noticing wifi disconnects randomly, speeds vary back and forth from 0.1Mbps to 100Mbps within a few seconds, can be up for a few seconds, or a few hours, not predictable. This might be some relevant information, but I looked through the modules and don't see anything like `rtw_8821ce`, there are `rtw88_*` modules which might be relevant, but in any case I can't map these to any packages as far as I can tell. ``` Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic ``` ``` *-network description: Wireless interface product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: b4:b0:24:d4:d7:ea width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtw_8821ce driverversion=6.5.0-15-generic firmware=N/A ip=192.168.2.52 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:33 ioport:e000(size=256) memory:f7c0-f7c0 ``` ``` 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b821 Subsystem: Realtek Semiconductor Co., Ltd. Device b821 Flags: bus master, fast devsel, latency 0, IRQ 33 I/O ports at e000 [size=256] Memory at f7c0 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-c8-21-01 Capabilities: [158] Latency Tolerance Reporting Capabilities: [160] L1 PM Substates Capabilities: [170] Precision Time Measurement Capabilities: [17c] Vendor Specific Information: ID=0003 Rev=1 Len=054 Kernel driver in use: rtw_8821ce Kernel modules: rtw88_8821ce ``` This was the best reference I can find: [WiFi frequently and randomly disconnects, rtw_8821ce driver][1], but even though it's in the "Newbie Corner" section, I'm not able to follow what they're doing. Like "Have you tried connecting with just wpa_supplicant (and a DHCP client if needed)?" is way over my skill level. This is the relevant output from `iwconfig`, I had just rebooted, as that sometimes helps for a bit, so the stats might not be representative: ``` wlp2s0IEEE 802.11 ESSID:"" Mode:Managed Frequency:5.785 GHz Access Point: 0E:**:**:**:**:0F Bit Rate=13 Mb/s Tx-Power=30 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=50/70 Signal level=-60 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:92 Invalid misc:0 Missed beacon:0 ``` And another output a few minutes later: ``` wlp2s0IEEE 802.11 ESSID:"" Mode:Managed Frequency:2.412 GHz Access Point: 0C:**:**:**:**:0D Bit Rate=58.5 Mb/s Tx-Power=30 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=62/70 Signal level=-48 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:9 Invalid misc:1 Missed beacon:0 ``` And after a few hours, note the speed looks really good, but the connection isn't working. I'm running off a hot spot now. ``` wlp2s0IEEE 802.11 ESSID:"" Mode:Managed Frequency:5.785 GHz Access Point: 0E:**:**:**:**:0F Bit Rate=175.5 Mb/s Tx-Power=30 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=39/70 Signal level=-71 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:146 Invalid misc:66 Missed beacon:0 ``` [1]: https://bbs.archlinux.org/viewtopic.php?id=273440 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-15-generic 6.5.0-15.15 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Lin
[Kernel-packages] [Bug 2051470] [NEW] Finding wifi is unstable in this release
You have been subscribed to a public bug: After a recent upgrade noticing wifi disconnects randomly, speeds vary back and forth from 0.1Mbps to 100Mbps within a few seconds, can be up for a few seconds, or a few hours, not predictable. This might be some relevant information, but I looked through the modules and don't see anything like `rtw_8821ce`, there are `rtw88_*` modules which might be relevant, but in any case I can't map these to any packages as far as I can tell. ``` Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic ``` ``` *-network description: Wireless interface product: Realtek Semiconductor Co., Ltd. vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: b4:b0:24:d4:d7:ea width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtw_8821ce driverversion=6.5.0-15-generic firmware=N/A ip=192.168.2.52 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:33 ioport:e000(size=256) memory:f7c0-f7c0 ``` ``` 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b821 Subsystem: Realtek Semiconductor Co., Ltd. Device b821 Flags: bus master, fast devsel, latency 0, IRQ 33 I/O ports at e000 [size=256] Memory at f7c0 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-c8-21-01 Capabilities: [158] Latency Tolerance Reporting Capabilities: [160] L1 PM Substates Capabilities: [170] Precision Time Measurement Capabilities: [17c] Vendor Specific Information: ID=0003 Rev=1 Len=054 Kernel driver in use: rtw_8821ce Kernel modules: rtw88_8821ce ``` This was the best reference I can find: [WiFi frequently and randomly disconnects, rtw_8821ce driver][1], but even though it's in the "Newbie Corner" section, I'm not able to follow what they're doing. Like "Have you tried connecting with just wpa_supplicant (and a DHCP client if needed)?" is way over my skill level. This is the relevant output from `iwconfig`, I had just rebooted, as that sometimes helps for a bit, so the stats might not be representative: ``` wlp2s0IEEE 802.11 ESSID:"" Mode:Managed Frequency:5.785 GHz Access Point: 0E:**:**:**:**:0F Bit Rate=13 Mb/s Tx-Power=30 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=50/70 Signal level=-60 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:92 Invalid misc:0 Missed beacon:0 ``` And another output a few minutes later: ``` wlp2s0IEEE 802.11 ESSID:"" Mode:Managed Frequency:2.412 GHz Access Point: 0C:**:**:**:**:0D Bit Rate=58.5 Mb/s Tx-Power=30 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=62/70 Signal level=-48 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:9 Invalid misc:1 Missed beacon:0 ``` And after a few hours, note the speed looks really good, but the connection isn't working. I'm running off a hot spot now. ``` wlp2s0IEEE 802.11 ESSID:"" Mode:Managed Frequency:5.785 GHz Access Point: 0E:**:**:**:**:0F Bit Rate=175.5 Mb/s Tx-Power=30 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=39/70 Signal level=-71 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:146 Invalid misc:66 Missed beacon:0 ``` [1]: https://bbs.archlinux.org/viewtopic.php?id=273440 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-15-generic 6.5.0-15.15 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: russell1179 F wireplumber /dev/snd/controlC1: russell1179 F wireplumber /dev/snd/controlC0: russell1179 F wireplumber /dev/snd/seq:russell1176 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun Jan 28 21:48:23 2024 InstallationDate: Installed on 2023-06-
[Kernel-packages] [Bug 2028165] Re: nvidia-dkms-* FTBS with linux 6.5
I've opened a jammy task for nvidia 390. We're getting a bunch of bug reports from jammy users complaining their Nvidia driver doesn't work anymore since they got automatically upgraded to kernel 6.5. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-450-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Jammy) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Jammy) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Jammy) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/2028165 Title: nvidia-dkms-* FTBS with linux 6.5 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-450-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-470 source package in Jammy: Invalid Status in nvidia-graphics-drivers-470-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-525 source package in Jammy: Invalid Status in nvidia-graphics-drivers-525-server source package in Jammy: Invalid Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Mantic: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-instance.c:13: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * ... [Fix] Apply the attached fix. [How to test] Install (and build) the patched packet. [Regression potential] The fix is composed of two patches: 1) the first patch simply garbage collect a reference to a function that was never used but that had the API changed in Linux 6.5 - so, it's a trivial change. 2) the second patch actually reimplement part of the vma scanning that was removed in __get_user_pages_locked() in upstream commit b2cac248191b7466c5819e0da617b0705a26e197 "mm/gup: removed vmas array from internal GUP functions" - here is where most likely any regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047658] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błęd
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug is no longer a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2047658 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I want to check if my nvidia is going well, so i use nvidia-smi and got error, then I processed to reinstall my nvidia drivers and got this error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Dec 28 21:10:15 2023 ErrorMessage: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 InstallationDate: Installed on 2022-09-13 (470 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/local/bin/python3.10, Python 3.10.7, unpackaged PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2047658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048934] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab de
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug is no longer a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2048934 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: driver bug while update ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: nvidia-kernel-source-390:amd64: Install nvidia-kernel-common-390:amd64: Install nvidia-dkms-390:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 10 21:00:05 2024 ErrorMessage: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück InstallationDate: Installed on 2023-04-21 (263 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2048934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049198] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-390, o script post-installation retornou
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug is no longer a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049198 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-390, o script post-installation retornou erro do status de saída 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: doesnt work ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 12 09:28:59 2024 ErrorMessage: o subprocesso instalado, do pacote nvidia-dkms-390, o script post-installation retornou erro do status de saída 10 InstallationDate: Installed on 2023-08-31 (134 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-390, o script post-installation retornou erro do status de saída 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049086] Re: General upgrade to 22.04 leads to second monitor not being recognised package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: usr/src/nvidia-390.157/dkms.conf]
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug is no longer a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049086 Title: General upgrade to 22.04 leads to second monitor not being recognised package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: usr/src/nvidia-390.157/dkms.conf] failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Upgraded using sudo apt upgrade Description: Ubuntu 22.04.3 LTS Release: 22.04 system fails to boot - blank screen - no activity recovery mode coaxed system to startup but error happens with nvidia drivers system has two monitors, one works (DVI) the second (VGA) does not. suspect ancient video card (geforce 610) and issues with compatibility ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: usr/src/nvidia-390.157/dkms.conf] ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: nvidia-kernel-source-390:amd64: Install nvidia-kernel-common-390:amd64: Install nvidia-dkms-390:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jan 11 15:20:51 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-07-30 (529 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 [modified: usr/src/nvidia-390.157/dkms.conf] failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049199] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug is no longer a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049199 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: le sous-processus paquet nvidia-dkms-390 script post- installation installé a renvoyé un état de sortie d'erreur 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Occurs first time during an update of Ubuntu. After that I was unable to boot ubuntu and gnome. I booted in recovery mode and desintalled all nvidia drivers with sudo apt remove '^nvidia'; apt autoremove And then reboot: ok (defaut driver nouveau for GPU Nvidia Quadro K610M) After that successfull reboot, I tried ubuntu-drivers autoinstall and got this error again. So I conclude that this package is in some way corrupted or no mode compatible whith that HW. Waiting for a solution, i desinstalled again nvidia* Thanks for your help. Daniel ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 12 13:40:53 2024 ErrorMessage: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 InstallationDate: Installed on 2021-10-27 (806 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 UpgradeStatus: Upgraded to jammy on 2022-05-02 (620 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049226] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug is no longer a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049226 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After software update only one screen is working with reduced resolution ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 12 18:55:09 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2022-04-23 (628 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049665] Re: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU)
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug is no longer a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049665 Title: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU) Status in linux-hwe-6.5 package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: A recent Ubuntu update is keeping the GPU software of Folding at Home (Folding@Home) from working. Past updates have not interfered with it. Expected result: An updated nvidia (proprietary) driver would be installed with the update that continues to work smoothly, provides OpenCL, etc. Actual result: The update caused FAH to disable its GPU processing capabilities. OpenCL is mentioned in the error message, so there may be something wrong with the OpenCL installation in the nVidia v390 package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 12:18:33 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.5.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] [10de:0fe9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 750M Mac Edition] [106b:011e] InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05ac:828d Apple, Inc. Bluetooth USB Host Controller Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 002: ID 05ac:8511 Apple, Inc. FaceTime HD Camera (Built-in) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. iMac14,3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=567a07dc-70f9-441e-a456-151c0da1e7ea ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 433.140.2.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-77EB7D7DAF985301 dmi.board.vendor: Apple Inc. dmi.board.version: iMac14,3 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-77EB7D7DAF985301 dmi.modalias: dmi:bvnAppleInc.:bvr433.140.2.0.0:bd04/18/2022:br0.1:svnAppleInc.:pniMac14,3:pvr1.0:rvnAppleInc.:rnMac-77EB7D7DAF985301:rvriMac14,3:cvnAppleInc.:ct13:cvrMac-77EB7D7DAF985301:skuSystemSKU#: dmi.product.family: iMac dmi.product.name: iMac14,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049548] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug is no longer a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049548 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 01:43:33 2024 ErrorMessage: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 InstallationDate: Installed on 2024-01-16 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049245] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug is no longer a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049245 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: cannot select screen resolution other then 1024 X 768 after implementing the latest ubuntu update. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: nvidia-kernel-source-390:amd64: Install nvidia-kernel-common-390:amd64: Install nvidia-dkms-390:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jan 13 15:29:03 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-05-04 (253 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051149] Re: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problèmes de dépendances - laissé non configuré
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug is no longer a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2051149 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Il m'est impossible d'installer le package nvidia-driver-390 390.157-0ubuntu0.22.04.2 Code retour: Failed to install/upgrade: problèmes de dépendances - laissé non configuré Je rencontre désormais un problème d'affichage de l'écran Cette erreur me bloque donc d'autres installations de package Cordialement ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-driver-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: libgnutls30:amd64: Install libgnutls30:amd64: Configure NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Jan 24 17:22:05 2024 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2023-05-02 (266 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-driver-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049945] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug is no longer a duplicate of bug 2051436 Nvidia 390 Needs Patched for Kernel 6.5+ ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049945 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: After installing the kernel update to version 6.5, the screen resolution was disrupted. When I try to switch to the open nouveau driver, an error occurs. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 19 21:49:11 2024 ErrorMessage: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 InstallationDate: Installed on 2024-01-19 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 Thanks for the bug report. I've opened a jammy task in bug 2028165 to track this. ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2051436 Title: Nvidia 390 Needs Patched for Kernel 6.5+ Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Supposedly, this was solved in Ubuntu 23.10, but the package never made it out of the mantic-proposed repository: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16 Nor was it backported to Ubuntu 22.04 As a temporary measure, I uploaded a patched version to a PPA for Ubuntu 22.04 (and added a patch for 6.6/6.7): https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049665] Re: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU)
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 Now tracking in bug 2051436 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049665 Title: A recent Ubuntu update broke GPU processing in Folding@Home (nVidia GPU) Status in linux-hwe-6.5 package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: A recent Ubuntu update is keeping the GPU software of Folding at Home (Folding@Home) from working. Past updates have not interfered with it. Expected result: An updated nvidia (proprietary) driver would be installed with the update that continues to work smoothly, provides OpenCL, etc. Actual result: The update caused FAH to disable its GPU processing capabilities. OpenCL is mentioned in the error message, so there may be something wrong with the OpenCL installation in the nVidia v390 package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 12:18:33 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: bcmwl/6.30.223.271+bdcom, 6.5.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] [10de:0fe9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 750M Mac Edition] [106b:011e] InstallationDate: Installed on 2024-01-16 (1 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05ac:828d Apple, Inc. Bluetooth USB Host Controller Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 002: ID 05ac:8511 Apple, Inc. FaceTime HD Camera (Built-in) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. iMac14,3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=567a07dc-70f9-441e-a456-151c0da1e7ea ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 433.140.2.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-77EB7D7DAF985301 dmi.board.vendor: Apple Inc. dmi.board.version: iMac14,3 dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-77EB7D7DAF985301 dmi.modalias: dmi:bvnAppleInc.:bvr433.140.2.0.0:bd04/18/2022:br0.1:svnAppleInc.:pniMac14,3:pvr1.0:rvnAppleInc.:rnMac-77EB7D7DAF985301:rvriMac14,3:cvnAppleInc.:ct13:cvrMac-77EB7D7DAF985301:skuSystemSKU#: dmi.product.family: iMac dmi.product.name: iMac14,3 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032136] Re: System reboot to BIOS boot menu
Using this reboot=acpi parameter does not work for me to resolve the issue at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2032136 Title: System reboot to BIOS boot menu Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Ever since update of Linux kernel to 6.2.0-26, this laptop (Lenovo Thinkpad T520) on reboot, goes to a boot loop directly to the BIOS Boot menu. On from there, still stuck in that loop. It displays an error message just before the BIOS Boot menu, but flashes by too fast to actually make out what is there. If it shutdown, and cold boot, it boots normally to the Grub2 Boot menu. There is a problem somewhere. This machine is ZFS-On-Root. Another User says he is having this same problem, but on an LVM2 install. The common denominator seems to be the update to Linux kernel 6.2.0-26. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Aug 20 14:14:56 2023 InstallationDate: Installed on 2021-09-23 (696 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-17 (368 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2032136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032136] Re: System reboot to BIOS boot menu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2032136 Title: System reboot to BIOS boot menu Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Ever since update of Linux kernel to 6.2.0-26, this laptop (Lenovo Thinkpad T520) on reboot, goes to a boot loop directly to the BIOS Boot menu. On from there, still stuck in that loop. It displays an error message just before the BIOS Boot menu, but flashes by too fast to actually make out what is there. If it shutdown, and cold boot, it boots normally to the Grub2 Boot menu. There is a problem somewhere. This machine is ZFS-On-Root. Another User says he is having this same problem, but on an LVM2 install. The common denominator seems to be the update to Linux kernel 6.2.0-26. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Aug 20 14:14:56 2023 InstallationDate: Installed on 2021-09-23 (696 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-08-17 (368 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2032136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+
** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2051436 Title: Nvidia 390 Needs Patched for Kernel 6.5+ Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Supposedly, this was solved in Ubuntu 23.10, but the package never made it out of the mantic-proposed repository: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16 Nor was it backported to Ubuntu 22.04 As a temporary measure, I uploaded a patched version to a PPA for Ubuntu 22.04 (and added a patch for 6.6/6.7): https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
Same as LP#2042500 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980829 Title: System freeze after resuming from suspend due to PCI ASPM settings Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.0 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux-oem-6.5 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux-oem-6.5 source package in Kinetic: Invalid Bug description: For OEM-6.1 [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] Below commit fixed the issue, but not going to be merged into mainline. The patch is still under discussion and have other variance, and we already merged the origin patch into oem-6.0 and 5.15/5.19 for a year, so could consider it's safer for us. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ I also created a DMI quirk to make the patches only affects on listed platforms. [Test] The affected machines could suspend/resume well. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == For Jammy/Kinetic SRU [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ So, I created a DMI quirk to make the patches only affects on listed platforms. [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == For OEM-6.0 [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
New series of the patches https://patchwork.kernel.org/project/linux- pci/cover/20240128233212.1139663-1-david.e@linux.intel.com/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042500 Title: Fix after-suspend-mediacard/sdhc-insert test failed Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability for suspend/resume"") reverted saving and restoring of ASPM L1 Substates due to a regression that caused resume from suspend to fail on certain systems. However, we never added this capability back and this is now causing systems fail to enter low power CPU states, drawing more power from the battery. The original revert mentioned that we restore L1 PM substate configuration even though ASPM L1 may already be enabled. This is due the fact that the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state(). Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4 more closely by: 1) Do not restore ASPM configuration in pci_restore_pcie_state() but do that after PCIe capability is restored in pci_restore_aspm_state() following PCIe r6.0, sec 5.5.4. 2) ASPM is first enabled on the upstream component and then downstream (this is already forced by the parent-child ordering of Linux Device Power Management framework). 3) Program ASPM L1 PM substate configuration before L1 enables. 4) Program ASPM L1 PM substate enables last after rest of the fields in the capability are programmed. 5) Add denylist that skips restoring on the ASUS and TUXEDO systems where these regressions happened, just in case. For the TUXEDO case we only skip restore if the BIOS is involved in system suspend (that's forcing "mem_sleep=deep" in the command line). This is to avoid possible power regression when the default suspend to idle is used, and at the same time make sure the devices continue working after resume when the BIOS is involved. [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~ pcieport :00:1c.0: pciehp: Slot(5): Card not present rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device inaccessible rtsx_pci :05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [where the issue could happen] low, the patch works well on the reported malfunctioned ASUS platform too. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042500/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051468] [NEW] Fix snapcraftyaml.yaml for jammy:linux-raspi
Public bug reported: jammy:linux-raspi has snapcraft.yaml. This file was added more than a decade ago. It does not produce any sensible kernel snap. ** Affects: linux-raspi (Ubuntu) Importance: Medium Assignee: Masahiro Yamada (myamada) Status: New ** Changed in: linux-raspi (Ubuntu) Assignee: (unassigned) => Masahiro Yamada (myamada) ** Changed in: linux-raspi (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2051468 Title: Fix snapcraftyaml.yaml for jammy:linux-raspi Status in linux-raspi package in Ubuntu: New Bug description: jammy:linux-raspi has snapcraft.yaml. This file was added more than a decade ago. It does not produce any sensible kernel snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2051468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
The kernel documentation explicitly mentions mailing lists for other components but not the one being modified: FRAMEBUFFER CORE M: Daniel Vetter S: Odd Fixes T: git git://anongit.freedesktop.org/drm/drm-misc F: drivers/video/fbdev/core/ This seems to be a bug in the kernel documentation. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051436] Re: Nvidia 390 Needs Patched for Kernel 6.5+
Okay, I see bug 2035189 officially ended nvidia 390. I would suggest that it continue to be maintained in the unofficial graphics driver PPA if Ubuntu does not want it in their repository. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2051436 Title: Nvidia 390 Needs Patched for Kernel 6.5+ Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Supposedly, this was solved in Ubuntu 23.10, but the package never made it out of the mantic-proposed repository: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2028165/comments/16 Nor was it backported to Ubuntu 22.04 As a temporary measure, I uploaded a patched version to a PPA for Ubuntu 22.04 (and added a patch for 6.6/6.7): https://launchpad.net/~dtl131/+archive/ubuntu/nvidiaexp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2051436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
Same here during boot, running 6.5.0-15-generic on Ubuntu 23.10: $ dmesg | grep -C3 evict [ 10.769204] EXT4-fs (xvda1): mounted filesystem 446b2699-dd26-4b84-9ada-d0cb48d21c93 r/w with ordered data mode. Quota mode: none. [ 11.061845] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled [ 11.069288] XFS (xvdb): Mounting V5 Filesystem b2136bf4-6edc-4fb2-8ad9-1fc236c2671d [ 11.109335] evict_inodes inode f37fffda, i_count = 1, was skipped! [ 11.109345] evict_inodes inode e97e4ee2, i_count = 1, was skipped! [ 11.109348] evict_inodes inode 92d4f6b3, i_count = 1, was skipped! [ 11.109351] XFS (xvdb): Ending clean mount However, mounting succeeds and no ill effects so far: $ mount | grep xfs /dev/xvdb on /home type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota) $ xfs_info /dev/xvdb meta-data=/dev/xvdb isize=512agcount=4, agsize=1638400 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1finobt=1, sparse=1, rmapbt=1 = reflink=1bigtime=1 inobtcount=1 nrext64=0 data = bsize=4096 blocks=6553600, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=16384, version=2 = sectsz=4096 sunit=1 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037214 Title: evict_inodes inode xxx, i_count = 1, was skipped! Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Confirmed Bug description: Hi, during boot the kernel logs the following messages: # dmesg | grep evict_inodes [ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped! [ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped! [ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped! [ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped! [ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped! [ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped! [ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped! [ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped! [ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped! [ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped! [ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped! [ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped! [ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped! [ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped! Those messages are not displayed when I boot my system with a mainline Linux kernel. Moreover, in the mainline Linux source code, I do not find the lines where such a message could be printed. Therefore, those messages are probably caused by an Ubuntu patch. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-5-generic 6.5.0-5.5 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 4827 F wireplumber /dev/snd/seq:bonnaudl 4808 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Sep 24 14:39:10 2023 MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor tpm_tis.interrupts=0 preempt=full split_lock_detect=off 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-6.5.0-5-generic N/A linux-backports-modules-6.5.0-5-generic N/A linux-firmware 20230919.git3672ccab-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2022 dmi.bios.release: 7.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.16NRTR4 dmi.board.asset.tag: Tag 12345 dmi.board.name: NS50_70MU dmi.board.vendor: TUXEDO dmi.board.version: Applicable dmi.chassis.asset.tag: No Asset Tag
[Kernel-packages] [Bug 2051342] Re: Enable lowlatency settings in the generic kernel
Before my post yesterday, I had never used the stress-ng utility, and only did so to repeat the originally posted test case. However, there was run to run variability with the stress-ng test that I could not understand for a 100% user, 0% system, type program. I decided to retest using one my own CPU loading programs. I also did only 1 thread and forced CPU affinity. I also tried to get a more accurate estimate of the tick ISR execution time. Trace only does time stamping to the microsecond, making it difficult. For the 1000Hz kernel and a 100 second trace, 10 tick ISRs were captured. min 0, average 0.7, max 2 uSec. 250Hz kernel test time (less is better): 300.14 seconds (100% user 0% system). For the 1000 Hertz kernel the extra execution time prediction is: 0.7 uSec/tick * 750 extra ticks/sec * 300.14 sec = 0.16 sec For a predicted execution time of 300.30 seconds. 1000Hz kernel test time: 300.32 seconds. 1000Hz+nohz_full test time: 300.08 seconds. In an attempt to get a better model the processor CPU frequency was changed from 4.8 GHz to 0.80 GHz. Tick ISR: min 3, average 4.0, max 11 uSec. Note: of the 10 tick ISRs captured the 11 uSec one was a one time outlier. 250Hz kernel test time: 429.25 For the 1000 Hertz kernel the extra execution time prediction is: 4.0 uSec/tick * 750 extra ticks/sec * 429.25 sec = 1.29 sec For a predicted execution time of 430.53 seconds. 1000Hz kernel test time: 430.38 seconds. -- 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/2051342 Title: Enable lowlatency settings in the generic kernel Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: [Impact] Ubuntu provides the "lowlatency" kernel: a kernel optimized for applications that have special "low latency" requirements. Currently, this kernel does not include any specific UBUNTU SAUCE patches to improve the extra "low latency" requirements, but the only difference is a small subset of .config options. Almost all these options are now configurable either at boot-time or even at run-time, with the only exception of CONFIG_HZ (250 in the generic kernel vs 1000 in the lowlatency kernel). Maintaining a separate kernel for a single config option seems a bit overkill and it is a significant cost of engineering hours, build time, regression testing time and resources. Not to mention the risk of the low-latency kernel falling behind and not being perfectly in sync with the latest generic kernel. Enabling the low-latency settings in the generic kernel has been evaluated before, but it has been never finalized due to the potential risk of performance regressions in CPU-intensive applications (increasing HZ from 250 to 1000 may introduce more kernel jitter in number crunching workloads). The outcome of the original proposal resulted in a re-classification of the lowlatency kernel as a desktop- oriented kernel, enabling additional low latency features (LP: #2023007). As we are approaching the release of the new Ubuntu 24.04 we may want to re-consider merging the low-latency settings in the generic kernel again. Following a detailed analysis of the specific low-latency features: - CONFIG_NO_HZ_FULL=y: enable access to "Full tickless mode" (shutdown clock tick when possible across all the enabled CPUs if they are either idle or running 1 task - reduce kernel jitter of running tasks due to the periodic clock tick, must be enabled at boot time passing `nohz_full=`); this can actually help CPU-intensive workloads and it could provide much more benefits than the CONFIG_HZ difference (since it can potentially shutdown any kernel jitter on specific CPUs), this one should really be enabled anyway, considering that it is configurable at boot time - CONFIG_RCU_NOCB_CPU=y: move RCU callbacks from softirq context to kthread context (reduce time spent in softirqs with preemption disabled to improve the overall system responsiveness, at the cost of introducing a potential performance penalty, because RCU callbacks are not processed by kernel threads); this should be enabled as well, since it is configurable at boot time (via the rcu_nocbs= parameter) - CONFIG_RCU_LAZY=y: batch RCU callbacks and then flush them after a timed delay instead of executing them immediately (c'an provide 5~10% power-savings for idle or lightly-loaded systems, this is extremely useful for laptops / portable devices - https://lore.kernel.org/lkml/20221016162305.2489629-3-j...@joelfernandes.org/); this has the potential to introduce significant performance regressions, but in the Noble kernel we already have a SAUCE patch that allows to enable/disable this option at boot time (see LP: #2045492), and by default it will be disabled (CONFIG_RCU_LAZY_DEFAULT_OFF=y) - CONFIG_HZ=1000 las
[Kernel-packages] [Bug 2048935] Re: Right speaker broken on Dell XPS 13 Plus 9320
Fresh install of Ubuntu 22.04.3 LTS with kernel 6.5.0-15-generic on Dell XPS 13 Plus 9320, the right speaker does not work. More precisely, as a user stated in the Dell forum "right channel audio is played by left speaker (lower one), and left audio comes from [the] other left speaker". Headphones and external speakers work fine. No apparent discrepancies of volume balance in Alsamixer. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048935 Title: Right speaker broken on Dell XPS 13 Plus 9320 Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: After upgrading from the previous HWE kernel 6.2.0-39-generic to the new HWE kernel 6.5.0-14-generic, the right speaker no longer works. When booting back into the old HWE kernel, the right speaker functions again. The left speaker works in both cases. Hardware info: Dell XPS 13 Plus 9320 with Intel i7 1260P Software info: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package info: apt-cache policy linux-generic-hwe-22.04 linux-generic-hwe-22.04: Installed: 6.5.0.14.14~22.04.7 Candidate: 6.5.0.14.14~22.04.7 Version table: *** 6.5.0.14.14~22.04.7 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages lspci output on kernel 6.5.0-14-generic: ``` 00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01) Subsystem: Dell Device 0af3 Flags: bus master, fast devsel, latency 64, IRQ 201, IOMMU group 15 Memory at 603e1d (64-bit, non-prefetchable) [size=16K] Memory at 603e00 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: sof-audio-pci-intel-tgl Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01) Subsystem: Dell Device 0af3 Flags: medium devsel, IRQ 16, IOMMU group 15 Memory at 603e1dc000 (64-bit, non-prefetchable) [size=256] I/O ports at efa0 [size=32] ``` aplay -l output on kernel 6.5.0-14-generic: ``` List of PLAYBACK Hardware Devices card 0: sofsoundwire [sof-soundwire], device 2: Speaker (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 5: HDMI 1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 6: HDMI 2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 7: HDMI 3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 21:40:02 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2022-06-25 (563 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2022-08-15 (513 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037762] Re: UBSAN: array-index-out-of-bounds in /build/linux-IPoq5q/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43
** Tags added: noble -- 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/2037762 Title: UBSAN: array-index-out-of-bounds in /build/linux- IPoq5q/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Mantic with linux 6.5 an error appears in dmesg: [ 10.281317] [ 10.281323] fbcon: Taking over console [ 10.281327] UBSAN: array-index-out-of-bounds in /build/linux-IPoq5q/linux-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2620:43 [ 10.281334] index 1 is out of range for type 'UCHAR [1]' [ 10.281338] CPU: 2 PID: 321 Comm: (udev-worker) Not tainted 6.5.0-5-generic #5-Ubuntu [ 10.281341] Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [ 10.281342] Call Trace: [ 10.281345] [ 10.281349] dump_stack_lvl+0x48/0x70 [ 10.281359] dump_stack+0x10/0x20 [ 10.281362] __ubsan_handle_out_of_bounds+0xc6/0x110 [ 10.281366] radeon_atombios_parse_power_table_4_5+0x3c9/0x3f0 [radeon] [ 10.281506] radeon_atombios_get_power_modes+0x205/0x210 [radeon] [ 10.281596] radeon_pm_init_dpm+0x8e/0x2f0 [radeon] [ 10.281709] radeon_pm_init+0xd0/0x100 [radeon] [ 10.281821] rv770_init+0x1fa/0x3d0 [radeon] [ 10.281933] radeon_device_init+0x540/0xa90 [radeon] [ 10.282021] radeon_driver_load_kms+0xcc/0x2f0 [radeon] [ 10.282111] drm_dev_register+0x10e/0x240 [drm] [ 10.282194] radeon_pci_probe+0xec/0x180 [radeon] [ 10.282280] local_pci_probe+0x47/0xb0 [ 10.282285] pci_call_probe+0x55/0x190 [ 10.282289] pci_device_probe+0x84/0x120 [ 10.282293] really_probe+0x1c7/0x410 [ 10.282297] __driver_probe_device+0x8c/0x180 [ 10.282300] driver_probe_device+0x24/0xd0 [ 10.282303] __driver_attach+0x10b/0x210 [ 10.282306] ? __pfx___driver_attach+0x10/0x10 [ 10.282309] bus_for_each_dev+0x8d/0xf0 [ 10.282316] driver_attach+0x1e/0x30 [ 10.282319] bus_add_driver+0x127/0x240 [ 10.282327] driver_register+0x5e/0x130 [ 10.282330] ? __pfx_radeon_module_init+0x10/0x10 [radeon] [ 10.282416] __pci_register_driver+0x62/0x70 [ 10.282419] radeon_module_init+0x4c/0xff0 [radeon] [ 10.282504] do_one_initcall+0x5e/0x340 [ 10.282510] do_init_module+0x68/0x260 [ 10.282514] load_module+0xba1/0xcf0 [ 10.282518] ? vfree+0xff/0x2d0 [ 10.282522] init_module_from_file+0x96/0x100 [ 10.282526] ? init_module_from_file+0x96/0x100 [ 10.282530] idempotent_init_module+0x11c/0x2b0 [ 10.282534] __x64_sys_finit_module+0x64/0xd0 [ 10.282537] do_syscall_64+0x5c/0x90 [ 10.282542] ? syscall_exit_to_user_mode+0x37/0x60 [ 10.282545] ? do_syscall_64+0x68/0x90 [ 10.282549] ? do_syscall_64+0x68/0x90 [ 10.282552] ? do_syscall_64+0x68/0x90 [ 10.282555] ? do_syscall_64+0x68/0x90 [ 10.282558] ? sysvec_call_function+0x4b/0xd0 [ 10.282567] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 10.282574] RIP: 0033:0x7f94cb925c5d [ 10.282591] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48 [ 10.282594] RSP: 002b:7ffcffbfa7b8 EFLAGS: 0246 ORIG_RAX: 0139 [ 10.282597] RAX: ffda RBX: 55b39a100500 RCX: 7f94cb925c5d [ 10.282599] RDX: 0004 RSI: 7f94cbb3c44a RDI: 0017 [ 10.282601] RBP: 7f94cbb3c44a R08: 0040 R09: fde0 [ 10.282602] R10: fe18 R11: 0246 R12: 0002 [ 10.282604] R13: 55b39a103ba0 R14: R15: 55b39a0fe210 [ 10.282607] [ 10.282611] ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-5-generic 6.5.0-5.5 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene 1346 F wireplumber /dev/snd/controlC1: eugene 1346 F wireplumber /dev/snd/seq:eugene 1345 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Sep 30 00:12:30 2023 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1630 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType:
[Kernel-packages] [Bug 2008774] Re: Ubuntu 22.04 not waking up after second suspend
Maybe related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031969 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 482380] Re: Sluggish system after "ACPI: EC: GPE storm detected"
Launchpad has imported 76 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=13502. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-06-10T20:04:11+00:00 sveina wrote: Starting in 2.6.30, using select() on any file under /proc/acpi/battery gives the wrong reply, in that it suggests they should be readable immediately but a read() call in fact blocks for 4-5 seconds. Prior to this, select worked correctly in that read in fact always returned immediately. This is on a MacBookPro4,1, as far as read-edid is concerned. I'll happily help with any further information you might find useful, although since I'm using this machine for work I can't take it offline to run a git-bisection. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/0 On 2009-06-10T20:10:47+00:00 akpm wrote: I marked this as a regression. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/1 On 2009-06-11T16:01:23+00:00 astarikovskiy wrote: please provide dmesg and acpidump outputs. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/2 On 2009-06-11T16:08:54+00:00 sveina wrote: Created attachment 21854 dmesg output at 20:41 hours uptime, including sleep Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/3 On 2009-06-11T16:09:19+00:00 sveina wrote: Created attachment 21855 acpidump output Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/4 On 2009-06-11T17:07:33+00:00 astarikovskiy wrote: please uncomment "#define DEBUG" at the beginning of drivers/acpi/ec.c and attach new dmesg. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/5 On 2009-06-11T20:15:17+00:00 sveina wrote: Of course that produces a humongous amount of output that overruns the kernel buffer in short order. Here's /var/log/messages instead, which means the boot messages are missing. The system switches from "sort of working" to "non-working" at ~21:59:26 in that log. "Sort of working" meaning reading it takes only 0.1 seconds on average, which is still a problem, but not as much of one. I don't really care about how long reading these files take. It can take a second, or a minute. However, select needs to work correctly on them. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/6 On 2009-06-11T20:15:59+00:00 sveina wrote: Created attachment 21860 kernel log w/debug on (16MB unpacked) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/7 On 2009-06-11T20:21:17+00:00 astarikovskiy wrote: select() never returned anything meaningful from /proc/acpi, it is just not implemented. So, the regression is 4 second read of battery instead of almost instant... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/8 On 2009-06-11T20:24:32+00:00 sveina wrote: That regression should be a separate bug, then. The one I reported was for select.. I suppose that's a WILL_NOT_FIX, if it's an old bug? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/9 On 2009-06-11T20:37:48+00:00 astarikovskiy wrote: it's a "feature" of procfs. There is no estimate on how long read from syntetic file takes. Yes, WILL_NOT_FIX is quite probable. You could edit the header to track the regression. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/482380/comments/10 On 2009-06-12T07:48:31+00:00 yakui.zhao wrote: Hi, Sveina From the acpidump it seems that the battery info is obtained by using the SMBUS controller that resides in the EC controller. But there also exists the acpi device of sbshc/sbs(battery). I don't know whether there exists the conflicts. Will you please disable "CONFIG_ACPI_SBS" in kernel configuration and see whether it still takes about 4-5 seconds to read the file of /proc/acpi/battery/* thanks. Reply
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Also having issues since Ubuntu 22.04 switched form kernel 6.2 to 6.5. Nothing obvious in the logs, and I'm also on an mt7921e driven wifi card, so this seems like a plausible cause [7.431847] mt7921e :03:00.0: enabling device ( -> 0002) [7.443046] mt7921e :03:00.0: ASIC revision: 79610010 [7.529484] mt7921e :03:00.0: HW/SW Version: 0x8a108a10, Build Time: 20220209150832a [7.791897] mt7921e :03:00.0: WM Firmware Version: 01, Build Time: 20220209150915 https://askubuntu.com/questions/1499938/kubuntu-22-04-wifi-freeze-after- hwe-kernel-upgrade-to-6-5-was-fine-on-6-2 -- 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/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: In Progress Bug description: The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007055] Re: cifs/samba mount not preserving file timestamps
Output of apt-get -s install cifs-utils: cifs-utils is already the newest version (2:6.14-1ubuntu0.1). Same for SAMBA: samba is already the newest version (2:4.15.13+dfsg-0ubuntu1.5). Hope that helps. -- 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/2007055 Title: cifs/samba mount not preserving file timestamps Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Incomplete Bug description: I think I've found a bug or regression in something when trying to mount a remote samba share. Modified/Created times are not properly preserved in newer versions of Ubuntu. Because of this, rsync thinks files are different based on their modified times and keeps re-syncing them. I have a NAS on my network, running samba. I have two devices, a desktop and laptop. Both are running Ubuntu, and set up the exact same way. The desktop is running ubuntu 20.04, the laptop 22.04. I have mounted the NAS on both devices the exact same way. I attempt to copy a file (rsync) the exact same way. On the 20.04 desktop, this works perfectly fine. On the 22.04 laptop, the modified times are not preserved and set to the current time, preventing things like rsync -t from working. The only difference i can find is that between the two systems, the newer laptop 22.04 mount adds a few more options than the older system to the cifs mount options. These are added automatically without being specified explicitly (see the mount -v output below): * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid * iocharset=utf8 added * serverino added desktop: $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.9-1ubuntu0.2 Candidate: 2:6.9-1ubuntu0.2 Version table: *** 2:6.9-1ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:6.9-1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ uname -a Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) laptop: $ lsb_release -rd Description:KDE neon 5.26 Release:22.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.14-1ubuntu0.1 Candidate: 2:6.14-1ubuntu0.1 Version table: *** 2:6.14-1ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:6.14-1build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ uname -a Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) the remote NAS is a synology appliance, running Samba version 4.10.18. SMB version 3 Steps to reproduce: 1. Similar setup, 1 device running 20.04, another running 22.04, otherwise up to date. 2. mount the NAS on both devices the exact same way $ sudo mount -t cifs -o vers=3.0,credentials=/etc/samba/smbcreds,iocharset=utf8,rw,uid=1000,gid=1000,dir_mode=0775,file_mode=0664 //nas/backup /media/scratch 3. on the 20.04 older desktop, create a test file and show the modify time $ fallocate -l 1M test1.txt $ stat test1.txt File: test1.txt Size: 1048576 Blocks: 2048 IO Block: 4096 regular file Device: 801h/2049d Inode: 13634663Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/desktop_user) Gid: ( 1000/desktop_user) Access: 2023-02-12 18:35:48.978743377 -0700 Modify: 2023-02-12 18:35:48.978743377 -0700 Change: 2023-02-12 18:35:48.978743377 -0700 Birth: - 4. rsync the test file to the mount, stat the file and see the modify/change are preserved $ rsync -avh test1.txt /media/scratch/ sending incremental file list test1.txt sent 1.05M bytes received 35 bytes 2.10M bytes/sec total size is 1.05M speedup is 1.00 $ stat /media/scratch/test1.txt File: /media/scratch/test1.txt Size: 1048576 Blocks: 2064 IO B