Ubuntu
linux package

Ubuntu 18.10 regression: nvidia driver does not work

Bug #1796730 reported by Alexey Balmashnov on 2018-10-08

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Fix Released	Undecided	Unassigned
	nvidia-graphics-drivers-390 (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

Problems started after upgrade to 18.10 and first reboot.
Symptoms:
* Login screen appears
* After providing credentials desktop does not start

---

Extra info for Bug 1796433

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-8-generic 4.18.0-8.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Mon Oct 8 20:01:33 2018
HibernationDevice: RESUME=UUID=45af239b-c597-45a1-bb72-3ba25b5ee546
InstallationDate: Installed on 2016-01-06 (1005 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.18.0-8-generic N/A
linux-backports-modules-4.18.0-8-generic N/A
linux-firmware 1.175
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to cosmic on 2018-10-05 (2 days ago)
dmi.bios.date: 09/16/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: HM65-MXM
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

See original description

Tags:

Revision history for this message

Alexey Balmashnov (a.balmashnov) wrote on 2018-10-08:

AlsaInfo.txt Edit (38.5 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (468 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (72.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (248 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (13.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (653 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (4.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1022 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (310 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (4.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.9 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (177.2 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (98.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Cristian Aravena Romero (caravena) wrote on 2018-10-08:

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19-rc7 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7/

Changed in linux (Ubuntu):
status:	New → Incomplete
description:	updated

Revision history for this message

Alexey Balmashnov (a.balmashnov) wrote on 2018-10-08:

make.log Edit (337.7 KiB, text/plain)

Yes it is started right after the upgrade from 18.04. 18.04 with the latest SW was running just fine (on kernel 4.15.0-36-generic). Have not seen it working on 18.10.

Tried 4.19-rc7.

Observations:
* Update manager "enables" driver, but it is not loaded
* Manual install of nvidia-driver-390 xserver-xorg-video-nvidia-390 shows the issue:
----------------
ERROR (dkms apport): kernel package linux-headers-4.19.0-041900rc7-generic is not supported
Error! Bad return status for module build on kernel: 4.19.0-041900rc7-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.87/build/make.log for more information.
----------------
Looks like compatibility issue with kernel 4.19. Not sure, though.

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Alexey Balmashnov (a.balmashnov) wrote on 2018-10-08:

Found patch [0] fixing module build. Observe the same behavior.

[0] https://www.hlmjr.com/index.php/2018/08/21/nvidia-drivers-390-77-vs-linux-kernel-4-18

tags:

added: kernel-bug-exists-upstream

Revision history for this message

Cristian Aravena Romero (caravena) wrote on 2018-10-09:

Hello,

In 'make.log':

'Makefile:958: "Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel"'

$ sudo apt install libelf-dev

And again try installing the nvidia driver, and if it does not work... Paste the make.log again.
--
Cristian Aravena Romero (caravena)

Revision history for this message

Alexey Balmashnov (a.balmashnov) wrote on 2018-10-09: Re: [Bug 1796730] Re: Ubuntu 18.10 regression: nvidia driver does not work

Also seen it. It was first thing I did. Forgot to mention it.

See comment #4 above: it was done with libelf-dev installed.

On Tue, Oct 9, 2018 at 1:10 PM Cristian Aravena Romero <email address hidden>
wrote:

> Hello,
>
> In 'make.log':
>
> 'Makefile:958: "Cannot use CONFIG_STACK_VALIDATION=y, please install
> libelf-dev, libelf-devel or elfutils-libelf-devel"'
>
> $ sudo apt install libelf-dev
>
> And again try installing the nvidia driver, and if it does not work...
> Paste the make.log again.
> --
> Cristian Aravena Romero (caravena)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1796730
>
> Title:
> Ubuntu 18.10 regression: nvidia driver does not work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+subscriptions
>

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-10-09:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers-390 (Ubuntu):
status:	New → Confirmed

Revision history for this message

NiBu (niko-buzki) wrote on 2018-10-09:

Nvidia-driver-installation.log Edit (11.8 KiB, text/plain)

installation log of nvidia-driver-390

Revision history for this message

NiBu (niko-buzki) wrote on 2018-10-09:

I have a very similar issue after upgrade to 18.10 (the system hangs after gdm login).

Revision history for this message

NiBu (niko-buzki) wrote on 2018-10-09:

#10

Booting in recovery mode and resuming normal start works.

Revision history for this message

Alexey Balmashnov (a.balmashnov) wrote on 2018-10-10:

#11

@NiBu what do you mean by: "Booting in recovery mode and resuming normal
start works."?

On Tue, 9 Oct 2018, 22:15 NiBu, <email address hidden> wrote:

> Booting in recovery mode and resuming normal start works.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1796730
>
> Title:
> Ubuntu 18.10 regression: nvidia driver does not work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+subscriptions
>

Revision history for this message

NiBu (niko-buzki) wrote on 2018-10-10:

#12

@a.balmashnov
If I boot in ubuntu "recovery mode" per grub (select something like "Ubuntu ... (recovery mode)" in grub menu and then select "resume" (see screenshots in https://wiki.ubuntuusers.de/Recovery-Modus/), gnome starts without any problems.

I think there is a race condition, causing the crash (loading nvidia driver?).

Revision history for this message

Alexey Balmashnov (a.balmashnov) wrote on 2018-10-14:

#13

Something in the updates made it work for me.

On the latest series of updates I've noticed kernel update to 4.18.0.9.10 and gave it a try. I still observe in dmesg diagnostics dump about "Bad or missing usercopy whitelist? Kernel memory exposure attempt..." but I am able to start session with nvidia driver up and running.

Revision history for this message

Cristian Aravena Romero (caravena) wrote on 2018-10-14:

#14

Hello Alexey,

Thanks! I close this report for your information delivered.

Best Regards,
--
Cristian Aravena Romero (caravena)

Changed in nvidia-graphics-drivers-390 (Ubuntu):
status:	Confirmed → Fix Released
Changed in linux (Ubuntu):
status:	Confirmed → Fix Released

Revision history for this message

Cristian Aravena Romero (caravena) wrote on 2018-10-14:

#15

Oummm... @NiBu,

You still have problems after the updates?

Best regards,
--
Cristian Aravena Romero (caravena)

Revision history for this message

NiBu (niko-buzki) wrote on 2018-10-14:

#16

Hey Cristian,

after today updates login works again - thank you.

Revision history for this message

Cristian Aravena Romero (caravena) wrote on 2018-10-14:

#17

@NiBu,

Excellent! Thank you.

Best regards,
--
Cristian Aravena Romero (caravena)

Revision history for this message

Diego Germán Gonzalez (diegogermangonzalez) wrote on 2018-10-25:

#18

I don't know if it's the same problem
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1798827
I did 3 installations from scratch and updated before installing the Nvidia driver and the problem persists.
In Ubuntu Budgie does not occur.

Brad Figg (brad-figg) on 2019-07-24

tags:

added: cscc

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

Ubuntu 18.10 regression: nvidia driver does not work

Bug Description

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package