Note, kdump will not work if the issue is a hardware reset. So if you do install kdump and test kdump and verify it works and then when it crashes you do not get a kdump then that points to a hardware issue. On one of my other systems, on reboot after a hw crash it detected that there were prior MCE errors and noted that on the boot back up, so it may be worth checking dmesg after reboot to see if MCE's were reported. On Wed, Oct 26, 2022 at 11:46 AM Jamie Fargen <jamie@xxxxxxxxxxxxxx> wrote: > > > > On Wed, Oct 26, 2022 at 9:06 AM Ken Smith via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: >> >> Hi everyone, >> >> I have a Dell Latitude 5480 laptop with a Fedora 36 install. It crashes >> regularly, uptime can sometimes be less that 5 mins but sometimes it >> lasts several hours. There is no trace at all in journalctl of its >> demise. It behaves like a machine with a memory issue. I've moved the >> memory from one slot to another and cleaned the connector. >> >> I've been using Redhat style systems for over 20 years and have known >> uptimes of several years. This laptop also boots Win10 and that install >> is stable. The machine passes Dells internal diagnostics. I'm travelling >> this week and don't have access to memtest86, but the Win10 memory test >> passes. Once I'm back home I can network boot it and run memtest86 and >> FC36 live - which will eliminate the ssd & its controller from the picture. >> . >> This machine has a KabbyLake processor (Intel Core i5-7200U 2.50GHz), 8G >> memory, an Intel i915 (HD Graphics 620) GPU and SSD storage. I've read >> on various forums that this combination of CPU/GPU can be problematic >> and some mentions that an upcoming Kernel release may contain a remedy >> for this. >> >> In addition to the FC36 standard kernel, I have tried a 6.0 kernel build >> and even the development 6.1 kernel from Rawhide's daily builds ( Beta >> for FC38 ) and its related firmware RPM. Also tried loading the 5.11 >> kernel from FC34. All with the same results. In fact the FC38 beta >> kernel only survives a few minutes even without the GUI. >> >> Is this hardware faulty, despite Win10 being stable? Does the Linux >> install stress the hardware in a way Win10 doesent. Should I hold on >> for a later kernel release with a fix. >> >> Is anyone else experiencing this issue? I'd value any insights. >> >> Many thanks >> >> Ken >> >> >> >> > > Ken- > > You should probably grab the kdump and post a BZ at http://bugzilla.redhat.com and maybe a kernel engineer can dig into the issue further. > > Here is a document on how to use kdumps > https://fedoraproject.org/wiki/How_to_use_kdump_to_debug_kernel_crashes > > > Regards, > -Jamie > >> > _______________________________________________ > 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 > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
