vmplayer 2.5.0. crashing on Ubuntu 8.10

[sofist81]

Hi!

I have found that vmplayer crashes a lot on Ubuntu 8.10 allways with the same error:

sofist@box:~$ vmplayer

Logging to /tmp/vmware-sofist/setup-7747.log

filename: /lib/modules/2.6.27-8-generic/misc/vmmon.ko

license: GPL v2

description: VMware Virtual Machine Monitor.

author: VMware, Inc.

srcversion: 96CBF0250D0FB3F01BFBFFC

depends:

vermagic: 2.6.27-8-generic SMP mod_unload modversions 586

filename: /lib/modules/2.6.27-8-generic/misc/vmnet.ko

license: GPL v2

description: VMware Virtual Networking Driver.

author: VMware, Inc.

srcversion: EC3F3B7348D1089CD1F884C

depends:

vermagic: 2.6.27-8-generic SMP mod_unload modversions 586

filename: /lib/modules/2.6.27-8-generic/misc/vmblock.ko

version: 1.1.2.0

license: GPL v2

description: VMware Blocking File System

author: VMware, Inc.

srcversion: 768B08090715A2D8C721BF3

depends:

vermagic: 2.6.27-8-generic SMP mod_unload modversions 586

parm: root:The directory the file system redirects to. (charp)

filename: /lib/modules/2.6.27-8-generic/misc/vmci.ko

license: GPL v2

description: VMware Virtual Machine Communication Interface (VMCI).

author: VMware, Inc.

srcversion: F400DF976CFE388EBC1A0A2

depends:

vermagic: 2.6.27-8-generic SMP mod_unload modversions 586

filename: /lib/modules/2.6.27-8-generic/misc/vsock.ko

license: GPL v2

version: 1.0.0.0

description: VMware Virtual Socket Family

author: VMware, Inc.

srcversion: EC2E0BE1F6FB039D1109ADB

depends: vmci

vermagic: 2.6.27-8-generic SMP mod_unload modversions 586

filename: /lib/modules/2.6.27-8-generic/misc/vmmon.ko

license: GPL v2

description: VMware Virtual Machine Monitor.

author: VMware, Inc.

srcversion: 96CBF0250D0FB3F01BFBFFC

depends:

vermagic: 2.6.27-8-generic SMP mod_unload modversions 586

(null): file autoDrawer.c: line 255 (ViewAutoDrawerUpdate): assertion failed: (grabbed)

vmpayer 2.5.0 build 118166 running on Ubuntu 8.10: Linux box 2.6.27-8-generic #1 SMP Thu Nov 6 17:33:54 UTC 2008 i686 GNU/Linux guest OS Windows XP SP 2

[nilsfr]

vmplayer 2.5.0 crashes when I use a wireless connection, but not when I use a wire. I use Ubuntu 8.10 with a 2.6.27-7-generic kernel and Windows XP SP 2 as a guest.

I experience a kernel panic just after my wireless get a connection. This just happen if the vmware kernel modules are running. If I start the kernel modules after a wireless connection has been established I do not get a kernel panic.

I do not know if it is relevant, but I have several of the following messages in my syslog:

Nov 18 09:42:37 faramir vmnetBridge: RTM_NEWLINK: name:eth1 index:3 flags:0x00001003
Nov 18 09:42:37 faramir vmnetBridge: Can't remove interface eth1 3 (does not exist).

This is the last /var/log/syslog entry before the panic:

Nov 18 10:05:26 faramir NetworkManager: <info>  Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.

In my /var/log/messages log I get:

Nov 18 10:05:24 faramir kernel: [http://171767.872812|http://171767.872812] bridge-eth1: is a Wireless Adapter

[nilsfr]

Just after I finished writing the previous post I got a kernel panic again this time this was the last syslog entries:

Nov 18 10:51:00 faramir NetworkManager: <info>  (eth1): supplicant connection state change: 7 -> 6 
Nov 18 10:51:00 faramir NetworkManager: <info>  (eth1): supplicant connection state change: 6 -> 7 
Nov 18 10:52:21 faramir vmnetBridge: RTM_NEWLINK: name:eth1 index:3 flags:0x00011043 
Nov 18 10:52:21 faramir vmnetBridge: Can't add interface eth1 3 (does exist). 
Nov 18 10:54:21 faramir vmnetBridge: RTM_NEWLINK: name:eth1 index:3 flags:0x00011043 
Nov 18 10:54:21 faramir vmnetBridge: Can't add interface eth1 3 (does exist). 
Nov 18 10:56:21 faramir vmnetBridge: RTM_NEWLINK: name:eth1 index:3 flags:0x00011043 
Nov 18 10:56:21 faramir vmnetBridge: Can't add interface eth1 3 (does exist). 
Nov 18 10:58:21 faramir vmnetBridge: RTM_NEWLINK: name:eth1 index:3 flags:0x00011043 
Nov 18 10:58:21 faramir vmnetBridge: Can't add interface eth1 3 (does exist). 
Nov 18 10:58:33 faramir vmnet-dhcpd: DHCPREQUEST for 192.168.77.129 from 00:0c:29:f6:67:c0 via vmnet8
Nov 18 10:58:33 faramir vmnet-dhcpd: DHCPACK on 192.168.77.129 to 00:0c:29:f6:67:c0 via vmnet8
Nov 18 11:00:01 faramir /USR/SBIN/CRON[13906]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
Nov 18 11:02:21 faramir vmnetBridge: RTM_NEWLINK: name:eth1 index:3 flags:0x00011043
Nov 18 11:02:21 faramir vmnetBridge: Can't add interface eth1 3 (does exist).
Nov 18 11:06:21 faramir vmnetBridge: RTM_NEWLINK: name:eth1 index:3 flags:0x00011043
Nov 18 11:06:21 faramir vmnetBridge: Can't add interface eth1 3 (does exist).
Nov 18 11:07:35 faramir dhclient: DHCPREQUEST of 192.168.1.111 on eth1 to 192.168.1.1 port 67

[nilsfr]

I have now tested with vmplayer 2.5.1 and kernel 2.6.27-9. The problem is still there.

I have found out one new thing. The bug is triggered if I use wireless, Pidgin and the vmware kernel modules. If I am using wireless and have the kernel services running I get a kernel panic when I start up Pidgin. I have not experienced this with other applications, but I have not done extensive testing.

Are there any chance that somebody who are able to fix this will read this thread? I hope this will not get lost among the numerous other posts. Perhaps I should create a separate thread for this? A kernel panic is a serious issue.

[nilsfr]

I am using vmplayer 2.5.1 on a 2.6.27-9 kernel, and this problem still exist. However, I have managed to narrow down the problem even futher. The kernel panic is triggered when using wireless, vmware kernel modules and Pidgin. More spesific it is the Bonjour protocol offered by Pidgin together with the vmware modules that triggers this kernel panic. If I use wireless and have the wmware modules running I get a kernel panic imediatley when I enable

a bonjour account in Pidgin. It seams like the bonjour protocol uses the network in a way that triggers a bug in the wmware modules, but only when using wireless.

Are there any chance that someone able to fix this will read this thread? Perhaps I should start a new thread for this specific issue? A kernel panic is a serious issue.

[nilsfr]

I am using vmplayer 2.5.1 on a 2.6.27-9 kernel, and this problem still exist. However, I have managed to narrow down the problem even futher. The kernel panic is triggered when using wireless, vmware kernel modules and Pidgin. More spesific it is the Bonjour protocol offered by Pidgin together with the vmware modules that triggers this kernel panic. If I use wireless and have the wmware modules running I get a kernel panic imediatley when I enable

a bonjour account in Pidgin. It seams like the bonjour protocol uses the network in a way that triggers a bug in the wmware modules, but only when using wireless.

Are there any chance that someone able to fix this will read this thread? Perhaps I should start a new thread for this specific issue? A kernel panic is a serious issue.

[RafaelBarreto]

I have this bug with vmware workstation (without any virtual machine installed).

When I hit a button (file, edit, view...) it opens the sub-list, but when I hit the button again to close the list, the program crashes (simply closes, getting me angry!)

The only message error that displays is:

(null): file autoDrawer.c: line 255 (ViewAutoDrawerUpdate): assertion failed: (grabbed)

I think it is some problem with gnome.

I use Ubuntu Intrepid with kernel 2.6.27.10.

[TigreDARK]

Hi I have Ubuntu 8.10 too: Linux 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux

I install VMware-Workstation-6.5.2-156735.i386.bundle

When I see the LOG FILE i have the same errors like you:::: /var/log/daemon.log

Apr 6 00:13:02 laptop vmnetBridge: Can't add interface ath0 4 (does exist).

Apr 6 00:14:17 laptop vmnetBridge: RTM_NEWLINK: name:ath0 index:4 flags:0x00011043

Apr 6 00:14:17 laptop vmnetBridge: Can't add interface ath0 4 (does exist).

Apr 6 00:15:32 laptop vmnetBridge: RTM_NEWLINK: name:ath0 index:4 flags:0x00011043

So I think... this is a vmnetBridge settings or something else!

I open VMWARE like root, so:

#sudo vmware

Then I go to : EDIT --->> VIRTUAL NETWORK EDITOR.

I see vmnet0 is BRIDGE MODE... I change it to NAT....

Simple like this!

I think if you have Kernel PANIC the problem is the drivers of Wireless. I have a Atheros, and drivers: madwifi-hal-0.10.5.6

This work very good for my Wireless. I have and HP PAVILLION DV 6000.

PD: If you have problems with Unity, I see if you use COMPIZ Fusion don't use "INDIRECT RENDERING" to see that install compiz fusion ICON (from synaptic).

Bye all!