Ubuntu 20.04 + Acer Nitro 5 + GTX1050 Mobile + nvidia 440.82 + freeze just after boot

I did a fresh installer on my notebook of ubuntu 20.04 LTS
install the suggested drivers

but after boot, on the login screen using the nvidia profile on prime select the hdmi crash and system freeze.

attached log file nvidia-bug-report.log (737.0 KB)

@generix I saw that you know much about this problem, could you help with that?

regards
Rafael Ribeiro

You’re getting an XID 79, gpu fallen off the bus error.
Please check for a bios update first, if that doesn’t help, try using the kernel parameter
intel_idle.max_cstate=1

tks…but I just checked the bios and I’m using the latest firmware version v1.28
https://www.acer.com/ac/pt/BR/content/support-product/7572?b=1

also, I included intel_idle.max_cstate=1 on kernel but still fail

new log uploaded
nvidia-bug-report.log (749.3 KB)

Did you check if it works in Windows?

Yes… I works perfectly.

But now I’m only using Ubuntu on it.

@generix
I did a fresh install and only include intel_idle.max_cstate=1 as kernel param

it still freeze but on other part

7 10:22:15 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) NVIDIA(GPU-0): WAIT (2, 8, 0x8000, 0x0000bf7c, 0x0000bf84)
mai 27 10:22:19 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) NVIDIA(0): The NVIDIA X driver has encountered an error; attempting to
mai 27 10:22:19 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) NVIDIA(0): recover…
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) NVIDIA(GPU-0): Failed to allocate notification memory.
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) NVIDIA(0): Failed to allocate push buffer
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) NVIDIA(0): Error recovery failed.
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) NVIDIA(0): *** Aborting ***
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE)
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: Fatal server error:
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) Failed to recover from error!
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE)
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE)
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: Please consult the The X.Org Foundation support
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: at http://wiki.x.org
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: for help.
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) Please also check the log file at “/var/log/Xorg.0.log” for additional information.
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE)
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE)
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) Backtrace:
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5649731eedec]
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f3c862b541f]
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) 2: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x4eda9) [0x7f3c8525d439]
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) 3: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x4ee9f) [0x7f3c8525d5cf]
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) 4: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x41054) [0x7f3c85241694]
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) 5: /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so (nvidiaAddDrawableHandler+0x41132) [0x7f3c85241a92]
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) 6: /lib/x86_64-linux-gnu/libX11.so.6 (nvidiaAddDrawableHandler+0x48c9cc) [0x7f3c85ad8c98]
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE)
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) Segmentation fault at address 0x14
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE)
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: FatalError re-entered, aborting
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE) Caught signal 11 (Segmentation fault). Server aborting
mai 27 10:22:30 nitro /usr/lib/gdm3/gdm-x-session[1050]: (EE)
log attached
nvidia-bug-report.log (854.0 KB)

Did you try to run something on it like a unigine demo while being on Windows?

no…but I run tensorflow using cuda and also able to connect through hdmi

Ok, should not be a general HW failure then.
Does this also happen when you boot while running on battery only?
Did you try installing Ubuntu 18.04 in case this is a kernel regression?

Ill try 18.04 version but Id like only to use the hdmi and monitor
not to do any heavy process

but seems very hard for this simple task.

do you have any special steps to install 18.04 + nvidia drivers?

regards

This is a low-level hw issue, this isn’t easy to fix.
Just install 18.04 and then install the drivers using Ubuntu’s Software&Drivers application. No special steps needed.
Did you try booting on battery?

hi @generix
I installed the version Ubuntu 19.10 (kernel 5.3.0-55-generic) + nvidia driver 435.21 (suggested on ubuntu-drivers)
and remove xorg.conf

now it is working like a charm
let’s see if it continues

tks for your support

Sound like a really awful kernel or driver regression, then.