Ask Your Question
1

Fedora 28 stuck randomly.

asked 2018-07-20 03:22:31 -0500

RidgeA gravatar image

Hi!

I'm using Fedora 28 with Gnome DE and xorg.

During this week I catch randomly freezes during normal work. After a freeze, the system stops responding at all and only one solution - hard reset. I can't do anything, including to switch to another TTY.

Last several lines in journalctl (sudo journalctl -l --boot=-1 --no-pager -n 100 --no-hostname -o short-iso) is :

2018-07-20T10:53:13+0300 systemd[5492]: Starting Tracker metadata extractor...
2018-07-20T10:53:13+0300 dbus-daemon[5572]: [session uid=1000 pid=5572] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
2018-07-20T10:53:13+0300 systemd[5492]: Started Tracker metadata extractor.
2018-07-20T10:53:24+0300 dbus-daemon[5572]: [session uid=1000 pid=5572] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.60' (uid=1000 pid=6033 comm="/usr/libexec/tracker-miner-fs ")
2018-07-20T10:53:24+0300 systemd[5492]: Starting Tracker metadata extractor...
2018-07-20T10:53:24+0300 dbus-daemon[5572]: [session uid=1000 pid=5572] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
2018-07-20T10:53:24+0300 systemd[5492]: Started Tracker metadata extractor.
2018-07-20T10:53:35+0300 dbus-daemon[5572]: [session uid=1000 pid=5572] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.60' (uid=1000 pid=6033 comm="/usr/libexec/tracker-miner-fs ")
2018-07-20T10:53:35+0300 systemd[5492]: Starting Tracker metadata extractor...
2018-07-20T10:53:35+0300 dbus-daemon[5572]: [session uid=1000 pid=5572] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
2018-07-20T10:53:35+0300 systemd[5492]: Started Tracker metadata extractor.
2018-07-20T10:53:46+0300 dbus-daemon[5572]: [session uid=1000 pid=5572] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.60' (uid=1000 pid=6033 comm="/usr/libexec/tracker-miner-fs ")
2018-07-20T10:53:46+0300 systemd[5492]: Starting Tracker metadata extractor...
2018-07-20T10:53:46+0300 dbus-daemon[5572]: [session uid=1000 pid=5572] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
2018-07-20T10:53:46+0300 systemd[5492]: Started Tracker metadata extractor.

but it doesn't give me a clue.

$ uname -r
4.17.6-200.fc28.x86_64

Could you point me out what I can do to enlighten the issue?

edit retag flag offensive close merge delete

Comments

Confirmed, I have the same random crash behaviour. Everything is OK booting with the former 4.17.3 kernel.

pasqua gravatar imagepasqua ( 2018-07-20 04:56:06 -0500 )edit

I've got exactly the same since a few days, it happens multiple times a day without me gving a clue of the cause. I think it happpens when I'm doing some gnome window manager intensive interaction, like opening apps, or moving windows. But also when I am opening new windows in Chrome (E.G. google Maps or so).

Already ran a Lenovo system check in Windows, but it remains completely stable then, and finds nothing (on My Lenovo Carbon X1 gen3)

LvdRee gravatar imageLvdRee ( 2018-07-20 05:35:26 -0500 )edit

Thank you. Today it happens while I was reading paper documents and just listening to music from PC. Maybe there are was some background tasks, though. I'll downgrade kernel version and see.

RidgeA gravatar imageRidgeA ( 2018-07-20 07:03:57 -0500 )edit

The same thing is happening here.

abitrolly gravatar imageabitrolly ( 2018-07-21 21:30:11 -0500 )edit

It appears to me that this problem was fixed temporarily but rhas appeared randomly various kernel releases. It is still happening on my system running fedora 28 kernel 5.0.5-5.0.5-100.fc28.x86_64100.fc28.x86_64. Sometimes the screen breaks into gibberish and just stays lit up and at other times the system is locked and can't be unlocked. In other words the system is down. Looking at logs all logging just stops without any info as to as error. This has been happening for quite a while now and is really frustrating. Long gone are the days when you went months without restart.

edwardc01 gravatar imageedwardc01 ( 2019-04-07 12:29:52 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
3

answered 2018-07-20 05:37:16 -0500

LvdRee gravatar image

it looks like it might be a kernel problem. You can try to test 4.17.7 see https://ask.fedoraproject.org/en/ques...

edit flag offensive delete link more

Comments

Thank you, I'll downgrade the kernel to the previous version.

RidgeA gravatar imageRidgeA ( 2018-07-20 07:04:31 -0500 )edit

My answer to my own question (which @LvdRee links to) contains instructions for how to upgrade to 4.17.7 from updates-testing. That kernel took a while to show up in the updates-testing repo but it's there now and the instructions worked for me. So upgrading may be a helpful option too.

ncj gravatar imagencj ( 2018-07-20 11:58:31 -0500 )edit

4.17.7-200.fc28.x86_64 is running stable at my system again

uptime 12:16:06 up 5 days, 21:55, 1 user, load average: 0,44, 0,29, 0,19

LvdRee gravatar imageLvdRee ( 2018-07-26 05:16:29 -0500 )edit

Question Tools

2 followers

Stats

Asked: 2018-07-20 03:22:31 -0500

Seen: 366 times

Last updated: Jul 20 '18