On 7/13/20 12:09 AM, Eshin Kunishima wrote:
I've met kernel hang-up without any stack trace from kernel 5.7.6 in the update testing repository. I did not find any usable messages in dmesg and journalctl(It said that its data was corruption after rebooting). Is there any method of collecting debug information in this situation?
Not after the fact.
Environment:
* Fedora 32 x86_64
* Kernel
* 5.7.6-200.fc32 @updates-testing?
* 5.7.7-200.fc32 @updates-testing
* 5.7.8-200.fc32 @updates-testing
* 5.7.8-200.fc32 (debug build)
* External modules
* nvidia 440.100-1.fc32 from rpmfusion
* zfs 6f1db
But kernel developers are not going to be interested anyway because you
have out-of-tree drivers, particularly the nvidia one.
_______________________________________________
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
