modprobe nvidia fails after suspend/resume cycle

Bug #1830170 reported by Rocko
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

My hyrbrid intel-nvidia system is set up to use the intel card by default, and the nvidia card power management is done by the kernel (I run a version of bbswitch that does no power management.)

After a reboot, the nvidia card on my hyrbrid intel-nvidia system is by default suspended by the kernel, but you can enable it by loading the module with "sudo modprobe nvidia". Using bumblebee, I can run programs on the nvidia card via optirun.

However, after a suspend/resume cycle, trying to load the nvidia module fails:

$ sudo modprobe nvidia
modprobe: ERROR: could not insert 'nvidia': No such device

This happens whether I disable bumblebeed.service or not via systemctl. It also happens if I load the nvidia module prior to suspending so the card is active. It also happens whether I'm doing a S0 sleep (mem_sleep = s2idle) or a S3 sleep (mem_sleep = deep).

In Ubuntu 18.10 this wasn't an issue, so it's a regression.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-16-generic 5.0.0-16.17
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rocko 6057 F.... pulseaudio
 /dev/snd/pcmC0D0p: rocko 6057 F...m pulseaudio
Date: Thu May 23 15:01:44 2019
HibernationDevice:
 # https://askubuntu.com/questions/1013830/slow-boot-due-to-long-kernel-load-time-18-04
 #RESUME=UUID=f48744af-908f-4614-9f8d-1295987f1246
 RESUME=none
InstallationDate: Installed on 2017-08-16 (644 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Dell Inc. XPS 15 9560
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-16-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 rcutree.rcu_idle_gp_delay=1 mem_sleep_default=deep vt.handoff=1
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-16-generic N/A
 linux-backports-modules-5.0.0-16-generic N/A
 linux-firmware 1.178.1
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2019-01-15 (127 days ago)
dmi.bios.date: 10/02/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.1
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-04-21T22:20:29.600541

Revision history for this message
Rocko (rockorequin) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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