[Kernel-packages] [Bug 2057805] Re: On Noble, system is locking up when attempting to log back in after being away for a few minutes
Just wanted to say, this is still happening regularly to me. I can work around it if I remember to put the system in suspend rather than simply locking the screen, but if I lock the screen and walk away for too long, the system is locked up aside from the alt-sysrq keys. I have a system where I can readily reproduce the issue and am happy to work with devs re: testing or possible fixes; would love to get this fixed before noble goes out the door. -- 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/2057805 Title: On Noble, system is locking up when attempting to log back in after being away for a few minutes Status in linux package in Ubuntu: New Bug description: Context: On my laptop, connected to battery power, if I lock the screen and come back sometime later (likely after the 10 minute "screen blank" threshold I have set in Gnome), I find that it does not come back up properly. * I have 3 monitors (2 external and one built-in), and when I move my mouse to wake up my machine, only the wallpaper on the built-in display seems to come back. * I get no login prompt. * I have no visible mouse cursor, and pressing Num Lock on my keyboard doesn't toggle any lights on the keyboard. * Ctrl-Alt-F1, -F2, etc., do not work. * The only way I know to get out of this is to either hard-reboot the machine or use the Alt-SysRq keys (e.g. the "reisub" combination). * /var/log/syslog and kern.log do show a general protection fault. Actually, 3 of them. (I had at least 3 lockups yesterday.) I've attached one as general_protection_fault.txt here; hopefully "ubuntu-bug linux" could capture the others if they are helpful. Additional context in case it is helpful: * I recently upgraded from Mantic to Noble for the purpose of dogfooding prior to formal release. I had some problems on Mantic with stability which had similar crashes, but they were more intermittent and did not generate the protection faults in syslog. Since upgrading to Noble, the lockups have changed from intermittent to predictable, i.e. if I lock my screen and walk away for at least 10 minutes, I fully expect to have to reboot my machine. I am running the 2013 model of the ASUS ROG M16 Zephyrus. It does use Nvidia Optimus, and while I suspect the problems I was encountering on Mantic were perhaps due to Nvidia driver bugs, the issues in Noble do appear to be different since the crashes are more consistent and appear to also generate the general protection fault errors in syslog. (I explain this since without this nuance, it may be easy to just suspect the nvidia driver is causing the problem.) Hopefully this helps; let me know if there's anything else I can provide to assist with this bug. Best Regards, Paul Goins ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 13 08:30:23 2024 InstallationDate: Installed on 2023-09-11 (184 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus M16 GU604VI_GU604VI ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=c8e79db4-8ec5-4855-89b4-aea8fb2c5b8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-07 (6 days ago) dmi.bios.date: 09/07/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GU604VI.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU604VI 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.ec.firmware.release: 0.68 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGU604VI.312:bd09/07/2023:br5.27:efr0.68:svnASUSTeKCOMPUTERINC.:pnROGZephyrusM16GU604VI_GU604VI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU604VI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus M16 dmi.product.name: ROG Zephyrus M16 GU604VI_GU604VI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage n
[Kernel-packages] [Bug 2057805] [NEW] On Noble, system is locking up when attempting to log back in after being away for a few minutes
Public bug reported: Context: On my laptop, connected to battery power, if I lock the screen and come back sometime later (likely after the 10 minute "screen blank" threshold I have set in Gnome), I find that it does not come back up properly. * I have 3 monitors (2 external and one built-in), and when I move my mouse to wake up my machine, only the wallpaper on the built-in display seems to come back. * I get no login prompt. * I have no visible mouse cursor, and pressing Num Lock on my keyboard doesn't toggle any lights on the keyboard. * Ctrl-Alt-F1, -F2, etc., do not work. * The only way I know to get out of this is to either hard-reboot the machine or use the Alt-SysRq keys (e.g. the "reisub" combination). * /var/log/syslog and kern.log do show a general protection fault. Actually, 3 of them. (I had at least 3 lockups yesterday.) I've attached one as general_protection_fault.txt here; hopefully "ubuntu-bug linux" could capture the others if they are helpful. Additional context in case it is helpful: * I recently upgraded from Mantic to Noble for the purpose of dogfooding prior to formal release. I had some problems on Mantic with stability which had similar crashes, but they were more intermittent and did not generate the protection faults in syslog. Since upgrading to Noble, the lockups have changed from intermittent to predictable, i.e. if I lock my screen and walk away for at least 10 minutes, I fully expect to have to reboot my machine. I am running the 2013 model of the ASUS ROG M16 Zephyrus. It does use Nvidia Optimus, and while I suspect the problems I was encountering on Mantic were perhaps due to Nvidia driver bugs, the issues in Noble do appear to be different since the crashes are more consistent and appear to also generate the general protection fault errors in syslog. (I explain this since without this nuance, it may be easy to just suspect the nvidia driver is causing the problem.) Hopefully this helps; let me know if there's anything else I can provide to assist with this bug. Best Regards, Paul Goins ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 13 08:30:23 2024 InstallationDate: Installed on 2023-09-11 (184 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus M16 GU604VI_GU604VI ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=c8e79db4-8ec5-4855-89b4-aea8fb2c5b8c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-07 (6 days ago) dmi.bios.date: 09/07/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: GU604VI.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU604VI 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.ec.firmware.release: 0.68 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrGU604VI.312:bd09/07/2023:br5.27:efr0.68:svnASUSTeKCOMPUTERINC.:pnROGZephyrusM16GU604VI_GU604VI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU604VI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus M16 dmi.product.name: ROG Zephyrus M16 GU604VI_GU604VI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Attachment added: "general_protection_fault.txt" https://bugs.launchpad.net/bugs/2057805/+attachment/5755616/+files/general_protection_fault.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057805 Title: On Noble, system is locking up when attempting to log back in after being away for a few minutes Status in linux package in Ubuntu: New Bug description: Context: On my laptop, connected to battery power, if I lock the screen and come back sometime later (likely after the 10 minute "screen blank" threshold I have set in Gnome), I find that it does not come back up properly. * I have 3 monitors (2 external and one built-in), and when I move my m
[Kernel-packages] [Bug 1914447] Re: geneve overlay network on vlan interface broken with offload enabled
I found this bug listed in a doc for a customer environment running Bionic, as something that was affecting them as well and for which we were waiting for a fix. I noticed today that this bug is only marked for focal and groovy. Is there a reason for this to be only focal and newer, or is it simply that it hadn't been reported for bionic yet? -- 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/1914447 Title: geneve overlay network on vlan interface broken with offload enabled Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [SRU Justification] Impact: In upstream v5.2 geneve tunnel stateless offload support was added to the mlx5 driver. This had some issue with VLANs where the VLAN ID was set by the driver even when offload support was enabled. Fix: Upstream (v5.11-rc3) commit 378d3783412e38dc3a2b9d524f551c0008ea314a "net/mlx5e: Fix SWP offsets when vlan inserted by driver" was backported (dropping some code because it did not yet exist in 5.8) and verified to address the problem. Testcase: Enable geneve tunnel offload support on a mlx5(e) card over VLAN. Regression potential: The modified code path is sending packets tagged for VLAN(s), so outgoing traffic into VLAN(s) would most likely be impacted. --- original description --- Mellanox Connect-X 5 network card When using geneve overlay networks over a vlan interface, txvlan offload currently has to be disabled as it interferes with the network traffic causing general wonkyness. Mellanox engineering pointed us at: https://www.spinics.net/lists/netdev/msg711911.html as a likely fix for this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 3 15:34:23 2021 ProcEnviron: TERM=screen-256color-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2021-02-03T15:17:01.792261 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914447/+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
