https://bugzilla.redhat.com/show_bug.cgi?id=1814682
--- Comment #44 from Alaa Hleihel (Mellanox) <ahlei...@redhat.com> --- Hi Liming, No, I am not using Fedora, I am using RHEL-8.1 (kernel-modules-extra-4.18.0-147.el8.aarch64). > kernel-modules-extra-5.7.0-0.rc0.git8.1.fc33.x86_64 This output was from Honggang, he just was checking the location of the cuse driver. > On the server where the problem exists, have we tried whether the kernel > module based driver works or not? If not working, the SmartNIC FW might be > stuck. We might need power-cycle to recover. Thanks! Yes, I did, and the kernel rshim driver worked fine on the same system. Reboot and power-cycle didn't help when using the user-space rshim. Note that I have an x86_64 system at Mellanox lab with RHEL-8.1 and everything worked well. For now, I see that the issue happens only on this aarch64 system (I don't have another arm system to try). Also, I've tried building upstream kernel v5.6 using the RHEL-8.1 .config file (+ enabling CONFIG_DEVMEM) and I got the same issue. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@lists.fedoraproject.org To unsubscribe send an email to package-review-le...@lists.fedoraproject.org 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/package-review@lists.fedoraproject.org
