Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

libmutter segfaulting when Nvidia drivers are installed (Fedora 26)

I recently got a Dell Precision 5520 with Nvidia discrete graphics and Optimus support and have been bringing it up with Fedora. I initially installed the machine with Fedora 25 and then almost immediately updated it to Fedora 26 since Fedora 26 became available shortly after I installed the machine with Fedora 25.

I would like to try out the proprietary graphics drivers on the machine, but apparently libmutter is segfaulting, preventing GDM from even coming up. I have tried the packaged Nvidia drivers from https://negativo17.org and RPMFusion, but the result is the same--basically, GDM never properly comes up due to a crash in _libmutter_ (so it seems).

Running _dmesg_ (retrieved using _journalctl -o short-precise -k -b -1_), I see:

Aug 10 21:29:59.795747 skutter kernel: gnome-shell[5609]: segfault at 28 ip 00007f6fe074a7e4 sp 00007ffc6b962300 error 4 in libmutter-0.so.0.0.0[7f6fe06fb000+13a000]

Using _journalctl -r_, I see:

Aug 10 21:30:00 skutter systemd-coredump[5617]: Process 5609 (gnome-shell) of user 42 dumped core.

                                                     Stack trace of thread 5609:
                                                     #0  0x00007f6fe074a7e4 center_pointer (libmutter-0.so.0)
                                                     #1  0x00007f6fe075ead9 meta_backend_x11_post_init (libmutter-0.so.0)
                                                     #2  0x00007f6fe075fb19 meta_backend_x11_cm_post_init (libmutter-0.so.0)
                                                     #3  0x00007f6fe0789586 meta_init (libmutter-0.so.0)
                                                     #4  0x0000557a42b081aa main (gnome-shell)
                                                     #5  0x00007f6fda1a64da __libc_start_main (libc.so.6)
                                                     #6  0x0000557a42b085ba _start (gnome-shell)

                                                     Stack trace of thread 5613:
                                                     #0  0x00007f6fda28aa9d poll (libc.so.6)
                                                     #1  0x00007f6fdbd6c569 g_main_context_iterate.isra.25 (libglib-2.0.so.0)
                                                     #2  0x00007f6fdbd6c902 g_main_loop_run (libglib-2.0.so.0)
                                                     #3  0x00007f6fdd891cb6 gdbus_shared_thread_func (libgio-2.0.so.0)
                                                     #4  0x00007f6fdbd93536 g_thread_proxy (libglib-2.0.so.0)
                                                     #5  0x00007f6fda55e36d start_thread (libpthread.so.0)
                                                     #6  0x00007f6fda296b8f __clone (libc.so.6)

                                                     Stack trace of thread 5614:
                                                     #0  0x00007f6fda291529 syscall (libc.so.6)
                                                     #1  0x00007f6fdbdb16fa g_cond_wait_until (libglib-2.0.so.0)
                                                     #2  0x00007f6fdbd40b31 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0)
                                                     #3  0x00007f6fdbd93ed4 g_thread_pool_thread_proxy (libglib-2.0.so.0)
                                                     #4  0x00007f6fdbd93536 g_thread_proxy (libglib-2.0.so.0)
                                                     #5  0x00007f6fda55e36d start_thread (libpthread.so.0)
                                                     #6  0x00007f6fda296b8f __clone (libc.so.6)

                                                     Stack trace of thread 5610:
                                                     #0  0x00007f6fda28aa9d poll (libc.so.6)
                                                     #1  0x00007f6fdbd6c569 g_main_context_iterate.isra.25 (libglib-2.0.so.0)
                                                     #2  0x00007f6fdbd6c67c g_main_context_iteration (libglib-2.0.so.0)
                                                     #3  0x00007f6fdbd6c6c1 glib_worker_main (libglib-2.0.so.0)
                                                     #4  0x00007f6fdbd93536 g_thread_proxy (libglib-2.0.so.0)
                                                     #5  0x00007f6fda55e36d start_thread (libpthread.so.0)
                                                     #6  0x00007f6fda296b8f __clone (libc.so.6)

                                                     Stack trace of thread 5615:
                                                     #0  0x00007f6fda28aa9d poll (libc.so.6)
                                                     #1  0x00007f6fdbd6c569 g_main_context_iterate.isra.25 (libglib-2.0.so.0)
                                                     #2  0x00007f6fdbd6c67c g_main_context_iteration (libglib-2.0.so.0)
                                                     #3  0x00007f6fb6f84f3d dconf_gdbus_worker_thread (libdconfsettings.so)
                                                     #4  0x00007f6fdbd93536 g_thread_proxy (libglib-2.0.so.0)
                                                     #5  0x00007f6fda55e36d start_thread (libpthread.so.0)
                                                     #6  0x00007f6fda296b8f __clone (libc.so.6)
Aug 10 21:30:00 skutter gnome-session[5570]: Unable to init server: Could not connect: Connection refused
Aug 10 21:30:00 skutter spice-vdagent[5623]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Aug 10 21:30:00 skutter gnome-session-binary[5570]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 10 21:30:00 skutter gnome-session-binary[5570]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Aug 10 21:30:00 skutter gnome-session-binary[5570]: Unrecoverable failure in required component org.gnome.Shell.desktop
Aug 10 21:30:00 skutter gnome-session[5570]: gnome-session-binary[5570]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 10 21:30:00 skutter gnome-session[5570]: gnome-session-binary[5570]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11

Here is some additional context for the _dmesg_ output (retrieved using _journalctl -o short-precise -k -b -1_):

Aug 10 21:29:56.627830 skutter kernel: nvidia: loading out-of-tree module taints kernel.
Aug 10 21:29:56.627965 skutter kernel: nvidia: module license 'NVIDIA' taints kernel.
Aug 10 21:29:56.627999 skutter kernel: Disabling lock debugging due to kernel taint
Aug 10 21:29:56.629807 skutter kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Aug 10 21:29:56.633768 skutter kernel: nvidia 0000:01:00.0: enabling device (0006 -> 0007)
Aug 10 21:29:56.634041 skutter kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 241
Aug 10 21:29:56.634062 skutter kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 PDT 2017 (using threaded interrupts)
Aug 10 21:29:56.635708 skutter kernel: nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 240
Aug 10 21:29:56.636769 skutter kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  375.66  Mon May  1 14:33:30 PDT 2017
Aug 10 21:29:56.637702 skutter kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Aug 10 21:29:56.637730 skutter kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
Aug 10 21:29:58.719801 skutter kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170119/nsarguments-95)
Aug 10 21:29:58.719857 skutter kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170119/nsarguments-95)
Aug 10 21:29:58.719877 skutter kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170119/nsarguments-95)
Aug 10 21:29:58.719894 skutter kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170119/nsarguments-95)
Aug 10 21:29:58.719920 skutter kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170119/nsarguments-95)
Aug 10 21:29:58.719936 skutter kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170119/nsarguments-95)
Aug 10 21:29:58.719957 skutter kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170119/nsarguments-95)
Aug 10 21:29:58.752513 skutter kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170119/nsarguments-95)
Aug 10 21:29:59.093774 skutter kernel: nvidia-modeset: Allocated GPU:0 (GPU-e4b6d7c0-c259-314b-0ede-b85e9556055d) @ PCI:0000:01:00.0
Aug 10 21:29:59.093928 skutter kernel: nvidia-modeset: Freed GPU:0 (GPU-e4b6d7c0-c259-314b-0ede-b85e9556055d) @ PCI:0000:01:00.0
Aug 10 21:29:59.634768 skutter kernel: show_signal_msg: 62 callbacks suppressed
Aug 10 21:29:59.634819 skutter kernel: gnome-shell[5590]: segfault at 28 ip 00007fb146b777e4 sp 00007fffe0ce1070 error 4 in libmutter-0.so.0.0.0[7fb146b28000+13a000]
Aug 10 21:29:59.795747 skutter kernel: gnome-shell[5609]: segfault at 28 ip 00007f6fe074a7e4 sp 00007ffc6b962300 error 4 in libmutter-0.so.0.0.0[7f6fe06fb000+13a000]
Aug 10 21:32:26.138104 skutter kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20170119/nsarguments-95)

If I remove all of the proprietary packages, things work again using the open source driver.

Here is the output from _lspci_:

00:00.0 Host bridge: Intel Corporation Device 5918 (rev 05)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05)
00:02.0 VGA compatible controller: Intel Corporation Device 591d (rev 04)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 05)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1c.1 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #2 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1)
00:1d.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #15 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
01:00.0 3D controller: NVIDIA Corporation GM107GLM [Quadro M1200 Mobile] (rev a2)
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
04:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 010f (rev 01)

Any suggestions on how to get this problem resolved?