How to troubleshoot hard system lockups?

asked 2018-08-05 16:45:26 -0500

lovepump gravatar image

Hello, With the upgrade (via dnf system-upgrade) to fedora 28 workstation I am facing several problems, but the worst of which is continual lockups within gnome. The entire system becomes unresponsive, and needs to be powered off/on. I've started a console session and ensured sshd has been started, yet when the lockup comes the ssh daemon doesn't accept connections. I can't kill and restart the machine remotely.

The only "oddities" my system has are: I have disabled ipv6, with a kernel parameter ipv6.disable = 1 My main grub2 boot menu no longer works (due to the upgrade to fedora 28), however I am able to launch fedora using an alternate EFI-enabled systemd launcher and choosing (chaining to) the fedora grub2 menu entry I had placed there in the past. I have changed the default systemd "runlevel" target to only boot to a console, and I start gnome (wayland?) manually with "startx". Machine is a Lenovo ideapad-110 with integrated intel graphics (according to lspci -vvvv, it is using the i915 kernel module)

I have the debug kernel installed if I need to use it in order to figure out what is going on. I have a USB to serial port adapter if it is necessary to debug from a remote machine.

Does anyone have experience or know any good resources with debugging hard lockups?

edit retag flag offensive close merge delete