Summary: | VMWare 4.5.1-build-7568 /dev/vmmon: fast clock rate 1044 -> 84 UI hang with gentoo-sources-2.4.26_pre5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Derek Berube <derek.berube> |
Component: | Current packages | Assignee: | Chris Gianelloni (RETIRED) <wolf31o2> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | brad, x86-kernel |
Priority: | High | ||
Version: | 2004.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
.config Used for Compiling The Kernel
.config File Used for Compiling the 2.4.25 Kernel .config File Used for Compiling the 2.4.26 Kernel .config File Used for Compiling the 2.4.22_r7 Kernel |
Description
Derek Berube
2004-03-26 09:40:21 UTC
Created attachment 28073 [details]
.config Used for Compiling The Kernel
The attached file is a copy of the .config file that I used to compile the
2.4.22-gentoo-r7 and the 2.4.26_pre5 kernels that I'm using.
Is that .config the actual one from the 2.4.26_pre5 or from the 2.4.22? I emerged the Gentoo-sources-2.4.26_pre6 and the same problem exists. The following is an excerpt from my system log. Mar 29 08:01:27 wildstar vmnet-dhcpd: DHCPINFORM from 192.168.228.130 Mar 29 08:01:27 wildstar /dev/vmmon: fast clock rate 84 -> 1044 Mar 29 08:01:27 wildstar Unable to handle kernel NULL pointer dereference at virtual address 00000000 Mar 29 08:01:27 wildstar printing eip: Mar 29 08:01:27 wildstar 00000000 Mar 29 08:01:27 wildstar *pde = 00000000 Mar 29 08:01:27 wildstar Oops: 0000 Mar 29 08:01:27 wildstar CPU: 0 Mar 29 08:01:27 wildstar EIP: 0010:[<00000000>] Tainted: PF Mar 29 08:01:27 wildstar EFLAGS: 00010286 Mar 29 08:01:27 wildstar eax: d2c8fb80 ebx: e5814000 ecx: f75f8240 edx: c01063e0 Mar 29 08:01:27 wildstar esi: f3e67700 edi: 00007005 ebp: e5815fe8 esp: e5815fac Mar 29 08:01:27 wildstar ds: 0018 es: 0018 ss: 0018 Mar 29 08:01:27 wildstar Process vmware-rtc (pid: 7736, stackpage=e5815000) Mar 29 08:01:27 wildstar Stack: f914db4d d2c8fb80 f3e67700 00007005 00000000 00000100 f914dad8 c0000000 Mar 29 08:01:27 wildstar eff7bd50 00000000 eff7bd8c 00000000 00000100 eff7bd50 00000000 eff7bd8c Mar 29 08:01:27 wildstar c01d170e f3e67700 f914dad8 00000001 00000000 Mar 29 08:01:27 wildstar Call Trace: [<f914db4d>] [<f914dad8>] [<c01d170e>] [<f914dad8>] Mar 29 08:01:27 wildstar Mar 29 08:01:27 wildstar Code: Bad EIP value. Mar 29 08:01:48 wildstar <7>/dev/vmmon: fast clock rate 1044 -> 84 I'm going to install the 2.4.25 Gentoo-sources build and see how things work under that release. I do not experience the problem/error with VMWare when using the 2.4.25 stable Gentoo-sources kernel. Created attachment 28363 [details]
.config File Used for Compiling the 2.4.25 Kernel
Created attachment 28364 [details]
.config File Used for Compiling the 2.4.26 Kernel
Created attachment 28365 [details]
.config File Used for Compiling the 2.4.22_r7 Kernel
Comment on attachment 28073 [details]
.config Used for Compiling The Kernel
This file can be removed. I've uploaded the .config files used for each of the
versions of the gentoo-sources that I've got running on my machine.
I changed my kernel configuration file so that the General setup -> RTC stores time in GMT option is not selected. After doing this, then recompiling my kernel I no longer get the error message when I run an embedded JVM in a VMWare virtual machine. I have another VMWare virtual machine which has the ServletExec servlet engine from New Atlanta Communications installed and running with IIS as well as the Remedy Action Request System E-Mail Engine both of which have/use embedded Java Virtual Machines. That VM used to hang with the reported error when I started it up as those services were configured to start on boot. Sorry. Looks like the error was just delayed. I was able to run the VMWare session and bring up the JVM; however, when I tried to shut down the VM, I encountered the error: Mar 30 08:57:03 wildstar /dev/vmmon: fast clock rate 84 -> 1044 Mar 30 08:57:03 wildstar Unable to handle kernel NULL pointer dereference at virtual address 00000000 Mar 30 08:57:03 wildstar printing eip: Mar 30 08:57:03 wildstar 00000000 Mar 30 08:57:03 wildstar *pde = 00000000 Mar 30 08:57:03 wildstar Oops: 0000 Mar 30 08:57:03 wildstar CPU: 0 Mar 30 08:57:03 wildstar EIP: 0010:[<00000000>] Tainted: PF Mar 30 08:57:03 wildstar EFLAGS: 00010286 Mar 30 08:57:03 wildstar eax: f78f0d80 ebx: da6e0000 ecx: f7437240 edx: c01063e0 Mar 30 08:57:03 wildstar esi: f37c1480 edi: 00007005 ebp: da6e1fe8 esp: da6e1fac Mar 30 08:57:03 wildstar ds: 0018 es: 0018 ss: 0018 Mar 30 08:57:03 wildstar Process vmware-rtc (pid: 3465, stackpage=da6e1000) Mar 30 08:57:03 wildstar Stack: f91b9b4d f78f0d80 f37c1480 00007005 00000000 00000100 f91b9ad8 c0000000 Mar 30 08:57:03 wildstar ee389d50 00000000 ee389d8c 00000000 00000100 ee389d50 00000000 ee389d8c Mar 30 08:57:03 wildstar c01d170e f37c1480 f91b9ad8 00000001 0002002e Mar 30 08:57:03 wildstar Call Trace: [<f91b9b4d>] [<f91b9ad8>] [<c01d170e>] [<f91b9ad8>] Mar 30 08:57:03 wildstar Mar 30 08:57:03 wildstar Code: Bad EIP value. Mar 30 08:57:21 wildstar <7>/dev/vmmon: fast clock rate 1044 -> 84 The above error was encountered with the 2.4.26_pre6 Gentoo Sources kernel. Just out of curiosity, does this occur with vanilla-sources? I will emerge the vanilla sources, recompile my kernel and then let you know. It looks like I still see the failure under the 2.4.25 Vanilla Sources. The following is what I believe are the relevant excerpts from the system log for this particualr paroblem. It looks like the problem happens at 15:01:17. I'll report this problem to VMWare, but I doubt I'll get anywhere since I'm technically not running a supported platform. Apr 12 14:58:25 wildstar /dev/vmmon: Module vmmon: registered with major=10 minor=165 Apr 12 14:58:25 wildstar /dev/vmmon: Module vmmon: initialized Apr 12 14:58:25 wildstar insmod: Warning: loading /lib/modules/2.4.25/misc/vmmon.o will taint the kernel: no license Apr 12 14:58:25 wildstar insmod: See http://www.tux.org/lkml/#export-tainted for information about tainted modules Apr 12 14:58:25 wildstar insmod: Warning: loading /lib/modules/2.4.25/misc/vmmon.o will taint the kernel: forced load Apr 12 14:58:25 wildstar insmod: Module vmmon loaded, with warnings Apr 12 14:58:25 wildstar insmod: Warning: loading /lib/modules/2.4.25/misc/vmnet.o will taint the kernel: no license Apr 12 14:58:25 wildstar insmod: See http://www.tux.org/lkml/#export-tainted for information about tainted modules Apr 12 14:58:25 wildstar insmod: Warning: loading /lib/modules/2.4.25/misc/vmnet.o will taint the kernel: forced load Apr 12 14:58:25 wildstar insmod: Module vmnet loaded, with warnings Apr 12 14:58:25 wildstar /dev/vmnet: open called by PID 6090 (vmnet-bridge) Apr 12 14:58:25 wildstar /dev/vmnet: hub 0 does not exist, allocating memory. Apr 12 14:58:25 wildstar /dev/vmnet: port on hub 0 successfully opened Apr 12 14:58:25 wildstar bridge-eth0: up Apr 12 14:58:25 wildstar bridge-eth0: attached Apr 12 14:58:26 wildstar /dev/vmnet: open called by PID 6107 (vmnet-natd) Apr 12 14:58:26 wildstar /dev/vmnet: hub 8 does not exist, allocating memory. Apr 12 14:58:26 wildstar /dev/vmnet: port on hub 8 successfully opened Apr 12 14:58:36 wildstar /dev/vmnet: open called by PID 6335 (vmnet-netifup) Apr 12 14:58:36 wildstar /dev/vmnet: port on hub 8 successfully opened Apr 12 14:58:36 wildstar vmnet-dhcpd: Internet Software Consortium DHCP Server 2.0 Apr 12 14:58:36 wildstar vmnet-dhcpd: Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. Apr 12 14:58:36 wildstar vmnet-dhcpd: All rights reserved. Apr 12 14:58:36 wildstar vmnet-dhcpd: Apr 12 14:58:36 wildstar vmnet-dhcpd: Please contribute if you find this software useful. Apr 12 14:58:36 wildstar vmnet-dhcpd: For info, please visit http://www.isc.org/dhcp-contrib.html Apr 12 14:58:36 wildstar vmnet-dhcpd: Apr 12 14:58:36 wildstar vmnet-dhcpd: Configured subnet: 192.168.228.0 Apr 12 14:58:36 wildstar vmnet-dhcpd: Setting vmnet-dhcp IP address: 192.168.228.254 Apr 12 14:58:36 wildstar /dev/vmnet: open called by PID 6358 (vmnet-dhcpd) Apr 12 14:58:36 wildstar /dev/vmnet: port on hub 8 successfully opened Apr 12 14:58:36 wildstar vmnet-dhcpd: Recving on VNet/vmnet8/192.168.228.0 Apr 12 14:58:36 wildstar vmnet-dhcpd: Sending on VNet/vmnet8/192.168.228.0 Apr 12 14:59:19 wildstar /dev/vmnet: open called by PID 7141 (vmware-vmx) Apr 12 14:59:19 wildstar /dev/vmnet: port on hub 8 successfully opened Apr 12 14:59:19 wildstar /dev/vmmon: fast clock rate 0 -> 19 Apr 12 14:59:35 wildstar /dev/vmmon: fast clock rate 19 -> 83 Apr 12 14:59:38 wildstar /dev/vmmon: fast clock rate 83 -> 84 Apr 12 15:00:25 wildstar vmnet-dhcpd: DHCPREQUEST for 192.168.228.129 from 00:0c:29:ae:83:6b via vmnet8 Apr 12 15:00:25 wildstar vmnet-dhcpd: DHCPACK on 192.168.228.129 to 00:0c:29:ae:83:6b via vmnet8 Apr 12 15:01:17 wildstar /dev/vmmon: fast clock rate 84 -> 1044 Apr 12 15:01:17 wildstar Unable to handle kernel NULL pointer dereference at virtual address 00000000 Apr 12 15:01:17 wildstar printing eip: Apr 12 15:01:17 wildstar 00000000 Apr 12 15:01:17 wildstar *pde = 00000000 Apr 12 15:01:17 wildstar Oops: 0000 Apr 12 15:01:17 wildstar CPU: 0 Apr 12 15:01:17 wildstar EIP: 0010:[<00000000>] Tainted: PF Apr 12 15:01:17 wildstar EFLAGS: 00213286 Apr 12 15:01:17 wildstar eax: f7913d80 ebx: f12c8000 ecx: f12c8000 edx: c03b2360 Apr 12 15:01:17 wildstar esi: f275fc80 edi: 00007005 ebp: f12c9fec esp: f12c9fb0 Apr 12 15:01:17 wildstar ds: 0018 es: 0018 ss: 0018 Apr 12 15:01:17 wildstar Process vmware-rtc (pid: 8320, stackpage=f12c9000) Apr 12 15:01:17 wildstar Stack: fa3f4a23 f7913d80 f275fc80 00007005 00000000 00000100 fa3f49ae c0000000 Apr 12 15:01:17 wildstar edc51d54 00000000 edc51d90 00000000 00000100 edc51d54 00000000 edc51d90 Apr 12 15:01:17 wildstar c010741e f275fc80 fa3f49ae edc50000 Apr 12 15:01:17 wildstar Call Trace: [<fa3f4a23>] [<fa3f49ae>] [<c010741e>] [<fa3f49ae>] Apr 12 15:01:17 wildstar Apr 12 15:01:17 wildstar Code: Bad EIP value. Apr 12 15:01:29 wildstar <7>/dev/vmmon: fast clock rate 1044 -> 84 I also wanted to indicate that this problem isn't related to JVM startup. I was trying to install a copy of OS/2 Warp 4 and the VMWare session UI hung with the same error message visible on my console. Right now, by default, I'm booting to the 2.4.25 Gentoo Sources kernel. I encountered the OS/2 failure running this version of the Kernel. When I installed and booted to the kernel compiled from the 2.4.25 Vanilla sources, I was able to reproduce the above error by starting up a VMWare session that runs a service which starts up JVM. The failure seems to be a little more intermittent than I had thought. Running the Gentoo Sources 2.4.25 kernel, I'm able get the error, but I wasn't able to get it by simply going to the JavaLobby web site. This time, I got the error message, by going to the JavaLobby web site doing some browsing around and then I tried to go to the remedy supportweb site: https://supportweb.remedy.com/arsys/apps/support/indexsecure.jsp VMWare doesn't seem to be hung per-se as I can click on the VMWare session and have mouse focus given to the VMWare session. I just can't click on anything in the VM session and get a resposne. I can press CTRL+ALT to get the mouse back and everything works fine in my LINUX environment. I cannot close the VMWare session. When I try to click on the button to close the window, I'm presented with a message box that indicates the VMWare session has not been powered down. It asks me if I'm sure that I want to close the VM. I indicate that I am and nothing happens. Based on VMWare's supported host operating systems page (http://www.vmware.com/products/desktop/ws_specs.html#hostos), they're only supporting up to 2.4.20 kernels. Given that I'm not running a supported host operating system and I don't have a support contract with VMWare, I don't think that I'll be able to get anywhere with them. I'll give it a shot though. I have the same exact problem as described by Derek Berube running VMware 4.5 with Debian linux (kernel 2.4.23). I'm running the Gentoo Dev Sources 2.6.5-r1 kernel and I can't reproduce the error. Sorry that this has been open for so long. Anyway, as I see it, this is an upstream problem. It is affecting vanilla-sources, which is, of course, unmodified by us, and also it is affecting Mike, who is running debian. |