I've been running F32 on a shiny new amd dual epyc workstation for about 1 year. The system is now remote to me and not convenient to access. About 1 week ago the system became unresponsive. I noticed errors logged about I/O errors, so I guessed it was an issue with the SSD. I went there and replaced the SSD with a shiny new samsung 1tb. Reinstalled F33 and got my vpns going so I could access again from home. But things are acting very strangely. Install was lightning fast. But after a while the machine becomes unusable. Any command takes minutes to react. I am unable to reboot it. sudo reboot after a very long time does nothing. I don't see anything interesting in /var/log/messages (I installed rsyslog). When I can eventually get top to run, I see systemd is in D state. There is plenty of free memory, and the machine has 64GB. I'm going to visit again and this time yank out the nvidia gpu. This is just a wild guess based on 1) it isn't critical for use right now 2) it places a load on the power supply just in case that's the issue 3) it's the only thing I can think to try. Just wondering if anyone has any thoughts on how to troubleshoot this. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
