[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Just an update, Nvidia seems to be aware of this, and they have confirmed tracking these issues. > We are tracking issue internally with bug number 3358939 . > We are currently trying to duplicate issue locally. > Shall keep everyone updated on it. Please see the Nvidia forum for updates. - https://forums.developer.nvidia.com/t/regression-460-series-black-screen-on-boot-nvidia-modeset-error-gpu-failed-to-allocate-display-engine-core-dma-push-buffer/165598/35 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ? do_vfs_ioctl+0x407/0x670 [ 325.011019] ? do_user_addr_fault+0x216/0x450 [ 325.011020] ? ksys_ioctl+0x67/0x90 [ 325.011021] ? __x64_sys_ioctl+0x1a/0x20 [ 325.011023] ? do_syscall_64+0x57/0x190 [ 325.011024]
[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Same issue with HP ZBook G3 with Quadro M1000M. Reverting to 450 drivers have resolved it for now, I also tried the 465 and 470 driver, these result in the same issue. There are various threads on the nvidia forum as well: - https://forums.developer.nvidia.com/t/regression-460-series-black-screen-on-boot-nvidia-modeset-error-gpu-failed-to-allocate-display-engine-core-dma-push-buffer/165598/8 - https://forums.developer.nvidia.com/t/regression-in-460-27-04-460-32-03-460-39-black-screen-nvidia-modeset-error-gpu-failed-to-allocate-display-engine-core-dma-push-buffer/167072/10 - https://forums.developer.nvidia.com/t/wake-from-sleep-freezes-with-460-driver/167231/2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ?
[Kernel-packages] [Bug 1849214] Re: "nvidia on-demand" mode does not support external displays
Just for future reference on the Nvidia Forum, this problem is mentioned in: https://forums.developer.nvidia.com/t/support-external-displays-in-render-offload-mode/107046/7 This make the whole On-Demand option impossible to use for me, and I was seeing forward to it so much. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1849214 Title: "nvidia on-demand" mode does not support external displays Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: In a recent driver, Nvidia finally added Linux support for render offload, where most graphics are rendered on the CPU-onboard GPU and only certain applications are rendered on the discrete Nvidia GPU. I know that Ubuntu 19.10 started shipping some updated Xorg packages to support this. For the most part the mode seems to work great. On my laptop, however, I have found that the "on demand" mode does not detect external monitors (and the monitor says it is not receiving a signal). Switching to "Nvidia" mode, where everything is rendered on the discrete GPU, makes the external displays work. The laptop is a Lenovo Thinkpad X1 Extreme (Gen 1). I have found this occurs both with nvidia-graphics-drivers-435 and nvidia-graphics-drivers-440 in the "graphics-drivers" ppa. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 13:17:38 2019 InstallationDate: Installed on 2019-09-04 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: Upgraded to eoan on 2019-10-21 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-04 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: nvidia_modeset nvidia Package: nvidia-driver-435 435.21-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: eoan third-party-packages Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-21 (0 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1849214/+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 1844728] Re: Lubuntu 19.04 login screen doesn't appear when using vmwgfx
Sorry I pressed the wrong button: I found a solution which was to torn wayland off: `sudo nano /etc/gdm3/custom.conf` and remove the # before, WaylandEnable=false. Sadly this did NOT fix my problems. -- 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/1844728 Title: Lubuntu 19.04 login screen doesn't appear when using vmwgfx Status in linux package in Ubuntu: Confirmed Bug description: I'm running Lubuntu in a qemu 2.12.1 VM. 18.04 works fine. When installing a fresh Lubuntu 19.04 or dist upgrade the 18.04 version the login screen doesn't appear anymore. Dropping to the console and typing `startx` launches the desktop successfully. Ubuntu 19.04 does not appear to have this problem so it's Lubuntu specific. The bug resembles this bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138 I use login manager sddm. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-29-generic 5.0.0-29.31 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Sep 19 23:03:33 2019 InstallationDate: Installed on 2019-09-19 (0 days ago) InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: lono wireless extensions. ens3 no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=950d7990-c633-42e3-94c6-75c812e71528 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Virtualization-2.4.0-11227-181219-0-g73d6e2e dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.2 dmi.modalias: dmi:bvnSeaBIOS:bvrVirtualization-2.4.0-11227-181219-0-g73d6e2e:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.2:cvnQEMU:ct1:cvrpc-i440fx-2.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844728/+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 1844728] Re: Lubuntu 19.04 login screen doesn't appear when using vmwgfx
I think I run into the same error. Ubuntu 19.04 used to run like a charm but since a recent update my laptop starts up into a black screen with a blinking cursor. I can run 'startx' from tty2 which will start an GUI. Which does not look like ubuntu but more similar to a native gnome GUI. I found a solution which was, to turn wayland off: (See https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1796614) -- 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/1844728 Title: Lubuntu 19.04 login screen doesn't appear when using vmwgfx Status in linux package in Ubuntu: Confirmed Bug description: I'm running Lubuntu in a qemu 2.12.1 VM. 18.04 works fine. When installing a fresh Lubuntu 19.04 or dist upgrade the 18.04 version the login screen doesn't appear anymore. Dropping to the console and typing `startx` launches the desktop successfully. Ubuntu 19.04 does not appear to have this problem so it's Lubuntu specific. The bug resembles this bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138 I use login manager sddm. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-29-generic 5.0.0-29.31 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Sep 19 23:03:33 2019 InstallationDate: Installed on 2019-09-19 (0 days ago) InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: lono wireless extensions. ens3 no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=950d7990-c633-42e3-94c6-75c812e71528 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Virtualization-2.4.0-11227-181219-0-g73d6e2e dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.2 dmi.modalias: dmi:bvnSeaBIOS:bvrVirtualization-2.4.0-11227-181219-0-g73d6e2e:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.2:cvnQEMU:ct1:cvrpc-i440fx-2.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844728/+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
