Ask Your Question
2

System Freezes and/or crashes after 4.17.5-100 in fedora 27

asked 2018-07-16 09:05:34 -0600

edwardc01 gravatar image

After upgrade to kernel 4.17.5-100 in fedora 27 workstation edition I'm seeing repeated crashes and or system freezes. System seems to run fine if I boot to kernel 4.17.3.100. Need help troubleshooting to see why 4.17.5.100 has problems.

Thanks

edit retag flag offensive close merge delete

Comments

1

You need to check your log files/journal to find out what component made your system freeze or crash. Use journalctl or the gnome-logs app, dmesg, and check Gnome's ABRT tool for reports.

florian gravatar imageflorian ( 2018-07-16 10:00:16 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2018-07-16 17:46:16 -0600

wangd gravatar image

If the freezes seem correlated with high usage of a USB device(s), it might be related to a regression present in fedora kernels after 4.17.3. https://bugzilla.redhat.com/show_bug....

Personally, I experienced hard hangs with kernel 4.17.5-200.fc28 when my daily backup began backing up to my external USB hard drive. At present time (2018-07-16 3:45pm PDT), the latest hang-free kernel seems to be 4.17.3. Try booting with that one, and if there are no crashes, you might consider using dnf versionlock to prevent kernel upgrades until the issue is resolved upstream.

edit flag offensive delete link more

Comments

Your answer seems to be what is really happening. My backup was running and it uses 2 external (USB 3.0) connected hard drives. After booting to 4.17.3-100 (Fedora 27) the backups ran fine and no system hangs.. However on subsequent updates a new kernel 5.17.6-100 is now installed. The backups haven't run under this kernel at this time. Is their a way to keep the 4.17.3-100 kernel around since the oldest one is removed on subsequent kernel upgrades?

edwardc01 gravatar imageedwardc01 ( 2018-07-19 08:26:06 -0600 )edit

should have said new kernel 4.17.6-100

edwardc01 gravatar imageedwardc01 ( 2018-07-19 08:27:31 -0600 )edit

On the bug report, it looks like this has been fixed with kernel 4.17.7-200. I don't know whether it's landed in updates yet, though. What I did was remove kernel versions after 4.17.3, and then run sudo dnf versionlock kernel-core. At some point, 4.17.7 will hit all the mirrors, and I can take off the versionlock and update. But no hurry for me--I don't have to be on the edge of kernel releases.

wangd gravatar imagewangd ( 2018-07-19 11:29:23 -0600 )edit

Thanks, I don't have to be on the edge of kernel releases either. I much prefer things to work as expected. Especially backups!

edwardc01 gravatar imageedwardc01 ( 2018-07-20 07:44:46 -0600 )edit

4.17.7 is available from dnf now, and has totally solved the problem for me!

murrayju gravatar imagemurrayju ( 2018-07-24 11:51:40 -0600 )edit

Question Tools

1 follower

Stats

Asked: 2018-07-16 09:05:34 -0600

Seen: 478 times

Last updated: Jul 16 '18