You are not logged in.

#1 2018-07-17 04:41:52

uint8
Member
Registered: 2018-07-17
Posts: 3

Unable to get Display Managers to display

Last Friday, I updated my HP ZBook 17 G2. I had some issues getting GDM to start and had to downgrade the nvidia-390xx drivers.

While getting that back to working order, I noticed I could not start any other display manager other than GDM.  The display goes black and nothing happens.  The log files don't show anything obvious to me.
Any ideas what I might be missing?  Thanks

gdm log (works).
sddm log
lightdm logs

# grep -Ev "^#" /etc/lightdm/lightdm.conf 
[LightDM]
minimum-vt=1
run-directory=/run/lightdm
sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions

[Seat:*]
session-wrapper=/etc/lightdm/Xsession

[XDMCPServer]

[VNCServer]
# grep -Ev "^#" /etc/gdm/custom.conf 

[daemon]
WaylandEnable=false

[security]

[xdmcp]

[chooser]

[debug]
Enable=true

Offline

#2 2018-07-17 06:36:06

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,885

Re: Unable to get Display Managers to display

Your kernel is 2 months old, so if you updated the X11 driver last friday, you conducted a partial update and the nvidia driver doesn't fit the kernel.
Post a complete dmesg and an actual xorg log (the thing in lightdm is only the stderr)

Offline

#3 2018-07-17 17:15:33

uint8
Member
Registered: 2018-07-17
Posts: 3

Re: Unable to get Display Managers to display

Sorry for the confusion.  I had downgraded from 4.17 to 4.16 try to figure out which upgraded package was the culprit.  The Nvidia drivers I happen to choose required kernel 4.16.
Anyway, I upgraded back to 4.17 and noticed the error in dmesg. I must not have seen it before.

To workaround the issue, I switched to nouveau.

Redhat bugzilla 1570493 points to this comment from Nvidia saying they're aware of it posted on 5/01.  There's a patch in the Redhat bugzilla report that supposedly fixes it.

Jul 17 10:28:24 (redacted) kernel: ------------[ cut here ]------------
Jul 17 10:28:24 (redacted) kernel: Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
Jul 17 10:28:24 (redacted) kernel: WARNING: CPU: 2 PID: 601 at mm/usercopy.c:81 usercopy_warn+0x7d/0xa0
Jul 17 10:28:24 (redacted) kernel: Modules linked in: joydev mei_wdt mousedev snd_hda_codec_hdmi ofpart cmdlinepart intel_spi_platform intel_spi spi_nor mtd iTCO_wdt iTCO_vendor_support gpio_ich ppdev hp_wmi sparse_keymap wmi_bmof mxm_wmi snd_hda_codec_idt nvidia_drm(PO) nvidia_modeset(PO) snd_hda_codec_generic intel_rapl arc4 x86_pkg_temp_thermal intel_powerclamp coretemp nls_iso8859_1 kvm_intel nvidia(PO) nls_cp437 vfat fat iwldvm kvm i915 mac80211 tpm_infineon irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel uvcvideo iwlwifi aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_uncore videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 intel_rapl_perf videobuf2_common videodev btusb btrtl btbcm btintel psmouse i2c_algo_bit input_leds bluetooth media drm_kms_helper snd_hda_intel cfg80211
Jul 17 10:28:24 (redacted) kernel:  drm snd_hda_codec ipmi_devintf snd_hda_core ipmi_msghandler snd_hwdep ecdh_generic snd_pcm rtsx_pci_ms intel_gtt memstick agpgart i2c_i801 rfkill snd_timer tpm_tis mei_me hp_accel tpm_tis_core syscopyarea parport_pc lis3lv02d snd lpc_ich tpm input_polldev sysfillrect battery parport sysimgblt rtc_cmos e1000e rng_core shpchp mei soundcore led_class fb_sys_fops wmi ie31200_edac evdev hp_wireless mac_hid ac vboxnetflt(O) vboxnetadp(O) vboxpci(O) vboxdrv(O) crypto_user ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 fscrypto sr_mod cdrom sd_mod rtsx_pci_sdmmc mmc_core serio_raw atkbd libps2 ahci libahci xhci_pci libata ehci_pci xhci_hcd ehci_hcd crc32c_intel scsi_mod rtsx_pci usbcore usb_common i8042 serio
Jul 17 10:28:24 (redacted) kernel: CPU: 2 PID: 601 Comm: Xorg Tainted: P           O      4.17.6-1-ARCH #1
Jul 17 10:28:24 (redacted) kernel: Hardware name: Hewlett-Packard HP ZBook 17/190A, BIOS L70 Ver. 01.34 10/28/2015
Jul 17 10:28:24 (redacted) kernel: RIP: 0010:usercopy_warn+0x7d/0xa0
Jul 17 10:28:24 (redacted) kernel: RSP: 0018:ffffbc16c3b03b60 EFLAGS: 00010286
Jul 17 10:28:24 (redacted) kernel: RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000001
Jul 17 10:28:24 (redacted) kernel: RDX: 0000000080000001 RSI: ffffffffb0e832be RDI: 00000000ffffffff
Jul 17 10:28:24 (redacted) kernel: RBP: 0000000000000001 R08: 0000000000000098 R09: 000000000000037b
Jul 17 10:28:24 (redacted) kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff9d6407645cb3
Jul 17 10:28:24 (redacted) kernel: R13: ffff9d6407645cb0 R14: 0000000000000000 R15: ffff9d6407645cf8
Jul 17 10:28:24 (redacted) kernel: FS:  00007fef33c76e00(0000) GS:ffff9d642ea80000(0000) knlGS:0000000000000000
Jul 17 10:28:24 (redacted) kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 17 10:28:24 (redacted) kernel: CR2: 00007fef2a9bf100 CR3: 0000000887ca0006 CR4: 00000000001606e0
Jul 17 10:28:24 (redacted) kernel: Call Trace:
Jul 17 10:28:24 (redacted) kernel:  __check_object_size+0xf0/0x180
Jul 17 10:28:24 (redacted) kernel:  os_memcpy_to_user+0x21/0x40 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  _nv009384rm+0xbf/0xe0 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? _nv028088rm+0x79/0x90 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? _nv028088rm+0x55/0x90 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? _nv013695rm+0xee/0x100 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? _nv015343rm+0x154/0x270 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? _nv008317rm+0x134/0x1a0 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? _nv008296rm+0x29c/0x2b0 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? _nv001072rm+0xe/0x20 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? _nv007324rm+0xd8/0x100 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? _nv001171rm+0x627/0x830 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? rm_ioctl+0x73/0x100 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? nvidia_ioctl+0x60/0x710 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? nvidia_ioctl+0x55a/0x710 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? nvidia_frontend_unlocked_ioctl+0x3a/0x50 [nvidia]
Jul 17 10:28:24 (redacted) kernel:  ? do_vfs_ioctl+0xa4/0x610
Jul 17 10:28:24 (redacted) kernel:  ? dput.part.5+0x9b/0x120
Jul 17 10:28:24 (redacted) kernel:  ? __fput+0x124/0x1e0
Jul 17 10:28:24 (redacted) kernel:  ? ksys_ioctl+0x60/0x90
Jul 17 10:28:24 (redacted) kernel:  ? __x64_sys_ioctl+0x16/0x20
Jul 17 10:28:24 (redacted) kernel:  ? do_syscall_64+0x5b/0x170
Jul 17 10:28:24 (redacted) kernel:  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jul 17 10:28:24 (redacted) kernel: Code: d6 e8 b0 41 51 4d 89 d8 48 c7 c0 34 cb e7 b0 49 89 f1 48 89 f9 48 0f 45 c2 48 c7 c7 e8 d6 e8 b0 4c 89 d2 48 89 c6 e8 0d f8 e2 ff <0f> 0b 48 83 c4 18 c3 48 c7 c6 be 32 e8 b0 49 89 f1 49 89 f3 eb 
Jul 17 10:28:24 (redacted) kernel: ---[ end trace e0aa4dc9dcf599a6 ]---

Offline

#4 2018-07-17 18:58:35

loqs
Member
Registered: 2014-03-06
Posts: 19,081

Re: Unable to get Display Managers to display

That warning with backtrace does not impact functionality.

Offline

#5 2018-07-17 19:54:46

uint8
Member
Registered: 2018-07-17
Posts: 3

Re: Unable to get Display Managers to display

Oh, my mistake for assuming!

Here is my dmesg if you don't mind taking a look https://dpaste.de/TTuu/raw.  I think I may be line-blind at this point.

Offline

#6 2018-07-17 20:00:28

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,885

Re: Unable to get Display Managers to display

There's no major problem w/ the nvidia kernel module, but this is an unconfigured optimus system and sddm & lightdm do not store the xorg log in the journal.
=> Please paste an xorg log and also be sure to read up https://wiki.archlinux.org/index.php/Optimus and follow ups.

Offline

Board footer

Powered by FluxBB