Hello.

I got an oops while I was running vmware-install.pl to upgrade
vmware-tools from VMware Workstation 6.0.2 to 6.0.4 on Ubuntu 7.10 on i386.
This may be a bug in vmware-tools kernel module, but I'm not sure.

Regards.
----------
[    0.000000] Linux version 2.6.22-14-generic (buildd@terranova) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Feb 12 07:42:25 UTC 2008 (Ubuntu 2.6.22-14.52-generic)
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000ca000 - 00000000000cc000 (reserved)
[    0.000000]  BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000001fef0000 (usable)
[    0.000000]  BIOS-e820: 000000001fef0000 - 000000001feff000 (ACPI data)
[    0.000000]  BIOS-e820: 000000001feff000 - 000000001ff00000 (ACPI NVS)
[    0.000000]  BIOS-e820: 000000001ff00000 - 0000000020000000 (usable)
[    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
[    0.000000] 0MB HIGHMEM available.
[    0.000000] 512MB LOWMEM available.
[    0.000000] found SMP MP-table at 000f6cd0
[    0.000000] Entering add_active_range(0, 0, 131072) 0 entries of 256 used
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA             0 ->     4096
[    0.000000]   Normal       4096 ->   131072
[    0.000000]   HighMem    131072 ->   131072
[    0.000000] early_node_map[1] active PFN ranges
[    0.000000]     0:        0 ->   131072
[    0.000000] On node 0 totalpages: 131072
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 4064 pages, LIFO batch:0
[    0.000000]   Normal zone: 992 pages used for memmap
[   ...
[ message continues ]

Hi Tetsuo, 

Is this bug reproducible ? 
Does this oops happen while the vmware-install script is still
executing ?
Or does it happen after the installation/upgrade is complete ?
If its the latter case, Can you please determine what line in the perl
script is triggering this oops ?
The only thing that is clear from the oops is that the kernel state is
corrupted. None of the vmware modules are yet loaded in the kernel.
I would like to isolate the problem to see if this corruption is being
caused by any of the VMware modules.

Thanks,

--

[ message continues ]

Hello.

It happened while /usr/bin/vmware-config-tools.pl is running.
I uploaded screenshots at the moment of oops.
http://I-love.SAKURA.ne.jp/tmp/oops-1.png
http://I-love.SAKURA.ne.jp/tmp/oops-2.png
The process who triggered this oops is "slabinfo".
So I tried "strace slabinfo" while I am running /usr/bin/vmware-config-tools.pl ,
and I found that the oops is happening while trying to read hgfsReqCache entry.
http://I-love.SAKURA.ne.jp/tmp/oops-4.png

Here is my environment:

 Host OS:

   CentOS 5.1 x86_64 on ThinkPad X60
   VMware workstation 6.0.4

 Guest OS:

   Ubuntu 7.10 i386
   Using NAT's DHCP for networking.

Regards.
--

[ message continues ]