Return to Level1Techs.com

Ubuntu 18.04 LTS Crash

linux
#1

Hi L1 brothers and sisters! My Linux box has been intermittently crashing / being unresponsive. Please advise how to troubleshoot this issue.

I think it is related to my video drivers. No crashing with the AMD Pro drivers. But I can’t play XCOM2. The AMD Open drivers cause the box to crash every couple of days. But I can play XCOM2.

I’m on Kernel version 5.2.3-050203-generic

Ubuntu 18.04.3 LTS - clean install. Same problem as before.

Radeon VII

These are the logs for the last hour before the system became unresponsive at 9:17 AM today. It stayed that way until 6:18 PM when I power cycled the box. The display would not come on and the numb lock would not turn off.

09:17

pam_unix(cron:session): session closed for user root

CRON

09:17

(root) CMD ( cd / && run-parts --report /etc/cron.hourly)

CRON

09:17

pam_unix(cron:session): session opened for user root by (uid=0)

CRON

09:03

Normal exit (0 jobs run)

anacron

09:03

Anacron 2.3 started on 2019-08-12

anacron

09:03

Started Run anacron jobs.

systemd

09:00

pam_unix(cron:session): session closed for user root

CRON

09:00

(root) LIST (root)

crontab

2

09:00

(root) CMD (timeshift --check --scripted)

CRON

09:00

pam_unix(cron:session): session opened for user root by (uid=0)

CRON

08:44

cannot get current kernel version: fork/exec /uname: no such file or directory

canonical-livepatch

4

08:44

JS method call WebChat.GetWebChatURL with 1 arguments

steam.desktop

08:44

No payload available.

canonical-livepatch

08:44

No updates available at this time.

canonical-livepatch

08:44

touched last check

canonical-livepatch

08:44

updating last-check

canonical-livepatch

08:44

Checking with livepatch service.

canonical-livepatch

08:44

cannot get current kernel version: fork/exec /uname: no such file or directory

canonical-livepatch

08:44

Client.Check

canonical-livepatch

08:17

pam_unix(cron:session): session closed for user root

CRON

08:17

(root) CMD ( cd / && run-parts --report /etc/cron.hourly)

CRON

08:17

pam_unix(cron:session): session opened for user root by (uid=0)

CRON

0 Likes

#2

was anything printed on the screen? if you have a GUI try hitting CTRL+ ALT F1-F6

maybe you can see the terminal but i doubt it if its not reading num lock

0 Likes

#3

Thanks! I’ll try that. I’m running Gnome. I’m not sure if that’s part of the issue.

Usually it is a blank screen - the display will say the source is not connected. But it is because after I power cycle the box, the display comes up.

0 Likes

#4

Your particular kernel is not the original LTS kernel Ubuntu ships with.
So my guess that the issue lays likely with that.

If you have ukuu installed and you manage to get into the gui desktop.
You want to try install the latest 4.15 LTS kernel.
And then reboot, selecting that said kernel via grub boot loader.

If you really need a 5.x series kernel for your newer hardware.
Then maybe double check which particular kernel the 19.04 intrim release ships with.
And then try that kernel instead.

0 Likes

#5

Or of course you could move on and install the 19.04 Disco Dingo interim release.
Which will be supported until October then 19.10 will make its its way up.

0 Likes

#6

Thanks for the ideas. For some reason ukuu downloads and installs new kernels. But I can’t get it to boot from 4.15 or something else.

I also tried grub-reboot and grub-set-default.

It’s time for some more Google action…

0 Likes

#7

sudo update-grub didn’t make a difference

0 Likes