Created attachment 1298558 [details] kernelbug with vmxnet3 Description of problem: Sometimes, when login or logout by ssh, system goes to freeze(nothing can be done except restart), and cpu goes to 100%(monitor by esxi) Version-Release number of selected component (if applicable): Fedora 26 fresh install in fact fedora 25 has the same problem. How reproducible: Steps to Reproduce: 1.login by ssh 2.type exit 3.login by ssh 4.type exit ...... sometimes freeze at first login or logout action, sometimes needs retry. Actual results: system freeze Expected results: system stay in normal state. Additional info: Fedora 26 installed on Esxi 6.5d open a console(not ssh), then login and type tail -f /var/log/messages when it's freeze, sometimes it will show the messages:
when it's freeze, sometimes it will show the messages: (please refer to the attachment 1298558 [details], sorry for this)
That bug halt is the result of buf_type field in the received descriptor from the hypervisor doesn't have the value VMXNET3_RX_BUF_PAGE. its possible that the latest hypervisor added a new buffer type that the fedora driver isn't ready for, but I don't see any update upstream that would suggest that. Can you add a stap script to dump out the value of buf_type at the bug halt to tell us what the reported type is?
How to dump out the value of buf_type. By the way, the hypervisor is esxi 6.5. And i found that if i change nic type from vmxnet3 to e1000e, the bug gone.
write a systemtap script to do it. Probe line 1310 of vmxnet3_drv.c (or the appropriate line for the specific kernel version you are using if its changed, and print $rbi->buf_type) And of yes, changing the driver fixes the problem, and thats expected. The problem you are reporting is a BUG halt that triggers when the vmxnet3 driver notes a problem with the virutal hardware descriptor that gets passed from the hypervisor. It would never happen with e1000 because it has different checks specific to its hardware.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.