pittperson
Contributor
Contributor

vmnet appears to cause ubuntu to freeze constantly

After about 4 days of uptime, my 14.04 Ubuntu box consistently locks up to the point where I have forcefully power it off in order to get it back.  Looking through kernel log it appears vmnet is causing this to happen.  Right before the freeze I see the following, any ideas?  I did not have this problem with 13.10.

Sep 21 18:21:06 stingray kernel: [  271.915036] /dev/vmmon[6444]: PTSC: initialized at 3410014000 Hz using TSC, TSCs are synchronized.

Sep 21 18:21:06 stingray kernel: [  272.010330] /dev/vmmon[6444]: Monitor IPI vector: 0

Sep 21 18:21:06 stingray kernel: [  272.474726] /dev/vmnet: open called by PID 6455 (vmx-vcpu-0)

Sep 21 18:21:06 stingray kernel: [  272.474738] device eth1 entered promiscuous mode

Sep 21 18:21:06 stingray kernel: [  272.474851] bridge-eth1: enabled promiscuous mode

Sep 21 18:21:06 stingray kernel: [  272.474852] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:21:09 stingray kernel: [  275.026797] /dev/vmnet: open called by PID 6502 (vmx-vcpu-0)

Sep 21 18:21:09 stingray kernel: [  275.026808] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:21:14 stingray kernel: [  280.525354] /dev/vmnet: open called by PID 6562 (vmx-vcpu-0)

Sep 21 18:21:14 stingray kernel: [  280.525365] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:40:33 stingray kernel: [ 1438.353753] /dev/vmnet: open called by PID 7732 (vmx-vcpu-0)

Sep 21 18:40:33 stingray kernel: [ 1438.353765] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:40:33 stingray kernel: [ 1438.354575] /dev/vmnet: open called by PID 7732 (vmx-vcpu-0)

Sep 21 18:40:33 stingray kernel: [ 1438.354581] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:40:33 stingray kernel: [ 1438.355321] /dev/vmnet: open called by PID 7732 (vmx-vcpu-0)

Sep 21 18:40:33 stingray kernel: [ 1438.355328] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:40:33 stingray kernel: [ 1438.356028] /dev/vmnet: open called by PID 7732 (vmx-vcpu-0)

Sep 21 18:40:33 stingray kernel: [ 1438.356034] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:40:36 stingray kernel: [ 1440.838604] /dev/vmnet: open called by PID 7764 (vmx-vcpu-0)

Sep 21 18:40:36 stingray kernel: [ 1440.838617] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:40:36 stingray kernel: [ 1440.839467] /dev/vmnet: open called by PID 7764 (vmx-vcpu-0)

Sep 21 18:40:36 stingray kernel: [ 1440.839474] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:40:36 stingray kernel: [ 1440.840323] /dev/vmnet: open called by PID 7764 (vmx-vcpu-0)

Sep 21 18:40:36 stingray kernel: [ 1440.840329] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:40:36 stingray kernel: [ 1440.841048] /dev/vmnet: open called by PID 7764 (vmx-vcpu-0)

Sep 21 18:40:36 stingray kernel: [ 1440.841054] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:43:19 stingray kernel: [ 1603.638380] /dev/vmnet: open called by PID 8118 (vmx-vcpu-0)

Sep 21 18:43:19 stingray kernel: [ 1603.638393] /dev/vmnet: port on hub 8 successfully opened

Sep 21 18:43:19 stingray kernel: [ 1603.638400] /dev/vmnet: open called by PID 8118 (vmx-vcpu-0)

Sep 21 18:43:19 stingray kernel: [ 1603.638404] /dev/vmnet: port on hub 8 successfully opened

Sep 21 18:43:19 stingray kernel: [ 1603.639227] /dev/vmnet: open called by PID 8118 (vmx-vcpu-0)

Sep 21 18:43:19 stingray kernel: [ 1603.639233] /dev/vmnet: port on hub 8 successfully opened

Sep 21 18:43:19 stingray kernel: [ 1603.639239] /dev/vmnet: open called by PID 8118 (vmx-vcpu-0)

Sep 21 18:43:19 stingray kernel: [ 1603.639242] /dev/vmnet: port on hub 8 successfully opened

Sep 21 18:43:19 stingray kernel: [ 1603.640026] /dev/vmnet: open called by PID 8118 (vmx-vcpu-0)

Sep 21 18:43:19 stingray kernel: [ 1603.640032] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:43:19 stingray kernel: [ 1603.640805] /dev/vmnet: open called by PID 8118 (vmx-vcpu-0)

Sep 21 18:43:19 stingray kernel: [ 1603.640811] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:43:23 stingray kernel: [ 1607.443627] /dev/vmnet: open called by PID 8150 (vmx-vcpu-0)

Sep 21 18:43:23 stingray kernel: [ 1607.443641] /dev/vmnet: port on hub 8 successfully opened

Sep 21 18:43:23 stingray kernel: [ 1607.443647] /dev/vmnet: open called by PID 8150 (vmx-vcpu-0)

Sep 21 18:43:23 stingray kernel: [ 1607.443650] /dev/vmnet: port on hub 8 successfully opened

Sep 21 18:43:23 stingray kernel: [ 1607.445754] /dev/vmnet: open called by PID 8150 (vmx-vcpu-0)

Sep 21 18:43:23 stingray kernel: [ 1607.445761] /dev/vmnet: port on hub 8 successfully opened

Sep 21 18:43:23 stingray kernel: [ 1607.445766] /dev/vmnet: open called by PID 8150 (vmx-vcpu-0)

Sep 21 18:43:23 stingray kernel: [ 1607.445769] /dev/vmnet: port on hub 8 successfully opened

Sep 21 18:43:23 stingray kernel: [ 1607.446506] /dev/vmnet: open called by PID 8150 (vmx-vcpu-0)

Sep 21 18:43:23 stingray kernel: [ 1607.446513] /dev/vmnet: port on hub 0 successfully opened

Sep 21 18:43:23 stingray kernel: [ 1607.447281] /dev/vmnet: open called by PID 8150 (vmx-vcpu-0)

Sep 21 18:43:23 stingray kernel: [ 1607.447287] /dev/vmnet: port on hub 0 successfully opened

0 Kudos
1 Reply
alexsch
Contributor
Contributor

I know this is an old issue, but I am still affected by it and have been since forever.

When I effectively get locked out my workstation, I remotely ssh in and everything appears idle by I also get similar messages just before it happens:

[ 3815.804312] /dev/vmmon[4400]: PTSC: initialized at 3999996000 Hz using TSC, TSCs are synchronized.

[ 3815.972228] /dev/vmmon[4400]: Monitor IPI vector: ff

[ 3815.972229] /dev/vmmon[4400]: HV      IPI vector: f2

When I stop vmware services via ssh, my workstation springs back into life.

Running Cinnamon on Linux Mint 19.1 Tessa.

0 Kudos