On 2020-06-25 17:39, Ed Greshko wrote:
On 2020-06-25 15:32, Qiyu Yan wrote:
That is mysterious, since a normal reset won't fix, I guess this have something to do with both your BIOS/UEFI and kernel.
That is to say, BIOS/UEFI gives wrong information to kernel and crashed a kernel driver. And the kernel thinks the oops is fatal and panicked.
I don't know the reason, but you can try to upgrade to latest release and try this again and see if the new kernel can survive from this. If same problem happens again, report them by abrt to bugzilla can help.
Maybe a bit quicker would be to boot the system with the most recent Live image and see if the
problem exists?
True, but as this server has many duties and keeps a large RAID I am hesitant to boot a Live image.
I will test after I upgrade to f32 (soon) as I do not expect fedora to spend much effort of the EOLed f30.
If the problem persists then I can see justification in submitting a BZ. Now I only want to hear if anyone
can make sense of the situation or even saw something similar.
--
Eyal at Home (fedora@xxxxxxxxxxxxxx)
_______________________________________________
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
