0

From last one month, I have been struggling to make Ubuntu 18.04 work on my newly assembled system with ASUS X299 Prime Deluxe motherboard and NVIDIA 1080Ti, SAMSUNG 970 EVO NVMe disk.

Has anyone tried this configuration ?

One noticable symptoom is that every day when I start the system, I get few call traces quickly after the grub menu, and after 2-3 hard reboots, the system will boot up login screen. After that throughout the day I don't see those call traces, but i start seeing random freezes after 5-15 mins of login from login screen.

I can't do anything (like going to console Ctrl-Alt-F2 etc) during the freeze which is annoying. If I were able to go to the console at least i could have debugged it a little further.

I tried intel_idle.max_cstate=1, nouveau.modeset=0, acpi=off, nomodeset, in various permutations and combinations, but nothing seems to work.

Call trace 1 : https://i.sstatic.net/IEV8m.jpg Call trace 2 : https://i.sstatic.net/xYrxx.jpg Call trace 3 : https://i.sstatic.net/7NqwP.jpg

I also saw this https://askubuntu.com/a/1025233/884359. Is this known problem with 18.04,if yes what is causing this problem ?

CPU temperature is bellow 45 deg. C and Power Supply is 1000W and the UPS connected to system shows Power usage below 200W always

Ubuntu is booted up with Legacy BIOS (UEFI BIOS and secure boot is disabled)

1 Answers1

0

You're having kernel panics. Somewhat difficult to diagnose, so lets try the basics first. fsck and memtest.

Step #1

Lets first check your file system for errors.

To check the file system on your Ubuntu partition...

  • boot to the GRUB menu
  • choose Advanced Options
  • choose Recovery mode
  • choose Root access
  • at the # prompt, type sudo fsck -f /
  • repeat the fsck command if there were errors
  • type reboot

If for some reason you can't do the above...

  • boot to a Ubuntu Live DVD/USB
  • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition
  • quit gparted
  • open a terminal window
  • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier
  • repeat the fsck command if there were errors
  • type reboot

Step #2

Boot to a Ubuntu Live DVD/USB and run memtest for at least one complete pass.

Report back.

heynnema
  • 73,649