new Fedora 28 - DRM: Pointer to TMDS table invalid

asked 2018-06-13 02:35:17 -0500

lados gravatar image

I have installed Fedora 28 on my second SSD.

My System:

  • 16 GB RAM Intel Core i7-8550U CPU @ 1.80GHz x 8
  • Graphis: Intel UHD Graphics 620 (Kabylake GT2) AND the Nvidia MX150 Therefore my Notebook has an Optimus graphics card due to the Nvidia MX150?

lspci | grep -E "VGA|3D" does print: 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1) and since I'm on fedora 28 I'm on wayland.

My GRUB has two entries: - Fedora (4.16.14-300) - Fedora (4.16.3-301)

When I'm booting in any of them I get this Message:

nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid Interesting thing: Both options will present the login screen (GDM). But mostly I only can successfully login into the second (not updated) option. The first option will mostly just show the grey background of the GDM.

And when I'm successfully in gnome, the System crashes regularly, with two failures:

  • xorg-x11-drv-nouveau
  • vmlinuz-4.16.14-300.fc28.x86_64

Details of xorg-x11-drv-nouveau:


WARNING: CPU: 4 PID: 386 at drivers/gpu/drm/nouveau/nvkm/subdev/pmu/base.c:86 nvkm_pmu_reset+0x14c/0x160 [nouveau]


WARNING: CPU: 4 PID: 386 at drivers/gpu/drm/nouveau/nvkm/subdev/pmu/base.c:86 nvkm_pmu_reset+0x14c/0x160 [nouveau] Modules linked in: rtsx_usb_sdmmc mmc_core rtsx_usb nouveau(+) i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper drm nvme crc32c_intel i2c_hid nvme_core serio_raw wmi video CPU: 4 PID: 386 Comm: systemd-udevd Not tainted 4.16.3-301.fc28.x86_64 #1 Hardware name: Timi TM1701/TM1701, BIOS XMAKB5R0P0502 10/13/2017


BOOT_IMAGE=/vmlinuz-4.16.3-301.fc28.x86_64 root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rhgb quiet LANG=en_US.UTF-8

Details of vmlinuz-4.16.14-300.fc28.x86_64


watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kworker/1:2:328]


watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kworker/1:2:328] Modules linked in: rfcomm ccm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security devlink cmac iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables bnep sunrpc vfat fat arc4 iwlmvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp iTCO_wdt iwlwifi iTCO_vendor_support kvm_intel hid_multitouch kvm snd_hda_codec_hdmi cfg80211 snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp irqbypass snd_soc_sst_ipc crct10dif_pclmul snd_soc_acpi crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel snd_soc_core snd_hda_codec_generic intel_cstate snd_compress intel_uncore snd_pcm_dmaengine ac97_bus intel_rapl_perf snd_hda_intel snd_hda_codec snd_usb_audio tpm_crb uvcvideo btusb snd_hda_core snd_usbmidi_lib videobuf2_vmalloc btrtl videobuf2_memops btbcm snd_rawmidi videobuf2_v4l2 snd_hwdep btintel videobuf2_common intel_wmi_thunderbolt snd_seq bluetooth videodev ax88179_178a usbnet snd_seq_device wmi_bmof mii rtsx_usb_ms snd_pcm memstick media joydev snd_timer snd mei_me ecdh_generic idma64 rfkill i2c_i801 mei soundcore intel_lpss_pci shpchp intel_lpss intel_pch_thermal tpm_tis intel_hid pinctrl_sunrisepoint tpm_tis_core ucsi_acpi sparse_keymap typec_ucsi tpm typec pinctrl_intel acpi_pad rtsx_usb_sdmmc mmc_core rtsx_usb nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper nvme drm nvme_core serio_raw i2c_hid crc32c_intel wmi video CPU: 1 PID: 328 Comm: kworker/1:2 ... (more)

edit retag flag offensive close merge delete


I would try diabling wayland, and should the problem go away, file a bug report. if the problem persists try removing nouveau and using rpm or proprietary nvidia driver, to see if that helps.

steveebey73742 gravatar imagesteveebey73742 ( 2018-06-13 07:05:28 -0500 )edit