i'm on gentoo x86_64 with a 2.6.19.1 kernel all works perfectly but the network on vmware. all works good but the networking. when i enable vmware bridged network in virtual machines, they reset. dmesg shows a kernel oops. /dev/vmmon[18617]: host clock rate change request 201 -> 1001 /dev/vmmon[18617]: host clock rate change request 1001 -> 201 /dev/vmnet: open called by PID 17924 () device eth0 entered promiscuous mode bridge-eth0: enabled promiscuous mode /dev/vmnet: port on hub 0 successfully opened skb_over_panic: text:ffffffff887d3dbd len:248 put:248 head:ffff81004c78dd0a data:ffff81004c78dc00 tail:ffff81004c78dc00 end:ffff81004c78dd80 dev:<NULL> ----------- [cut here ] --------- [please bite here ] --------- Kernel BUG at net/core/skbuff.c:93 invalid opcode: 0000 [1] SMP CPU 1 Modules linked in: vmnet(PF) vmmon(PF) fuse ohci1394 nvidia(P) ieee1394 i2c_i801 Pid: 18617, comm: vmware-vmx Tainted: PF 2.6.19.1 #25 RIP: 0010:[<ffffffff80425bed>] [<ffffffff80425bed>] skb_over_panic+0x5c/0x6f RSP: 0018:ffff81003b919ea8 EFLAGS: 00013296 RAX: 000000000000009b RBX: ffff81006bc77e80 RCX: ffffffff804ff328 RDX: ffffffff804ff328 RSI: 0000000000043092 RDI: ffffffff804ff320 RBP: ffff81003acf4a00 R08: 00000005af5448b8 R09: ffffffff8062e700 R10: 0000000000000001 R11: 0000000000000080 R12: 00000000000000f8 R13: 00000000000000f8 R14: 00000000f1b4f052 R15: ffff81004c78dc12 FS: 0000000000000000(0000) GS:ffff81007e317f40(0063) knlGS:00000000f35c9b90 CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b CR2: 00002ba97b73d080 CR3: 0000000051efc000 CR4: 00000000000006e0 Process vmware-vmx (pid: 18617, threadinfo ffff81003b918000, task ffff810055590000) Stack: ffff81004c78dc00 ffff81004c78dd80 ffffffff804aa7a0 ffffffff887d3dc8 0000000000000000 ffff81006b92e0c0 00000000000000f8 ffff81003b919f50 00000000f1b4f052 0000000000000000 0000000000000000 ffffffff887d2901 Call Trace: [<ffffffff887d3dc8>] :vmnet:VNetUserIfWrite+0xdb/0x11c [<ffffffff887d2901>] :vmnet:VNetFileOpWrite+0x49/0x50 [<ffffffff8021533d>] vfs_write+0xad/0x160 [<ffffffff80215d60>] sys_write+0x45/0x75 [<ffffffff8025af73>] sysenter_do_call+0x1b/0x67 Code: 0f 0b 68 5e 91 4c 80 c2 5d 00 48 83 c4 18 c3 00 00 00 00 48 RIP [<ffffffff80425bed>] skb_over_panic+0x5c/0x6f RSP <ffff81003b919ea8> <7>/dev/vmmon[18613]: host clock rate change request 201 -> 0 vmmon: Had to deallocate locked 18375 pages from vm driver ffff81006b88c000 vmmon: Had to deallocate AWE 3817 pages from vm driver ffff81006b88c000 i don't know if this is the right place to report such failures, can you contact the mainteiner?
Sadly we don't have direct contact with Vmware itself upstream, nor the university that produce the vmware-any-any sources (which contain heavily patched module sources for maximum compatibility across both vmware products and different kernels). The most I can recommend, unfortunately, is to check your CFLAGS and other portage compilation settings and remove any weird or unusual options you may have set. Also check that you haven't patched the vanilla kernel sources (other than perhaps with the standard gentoo patches which we test against). I'm afraid I'm not sure what else to recommend than that, but we'll leave the bug open in-case someone else can add some insight to the problem and suggest a solution (you might want to check the VMTN forums and see if anyone else has reported similar problems)...
Patrizio, could you please try recompiling your modules, and verify if this is still a problem? We're now using the vmware-any-any-update112, and this fixes many compilation issues on recent kernels. There is still an issue involving very recent kernels and amd64 machines, but that's an extremely low level problem and there is unlikely to be a fix for a while... Until I hear back, I'm going to mark this bug as TEST-REQUEST...
i bumped to vmware 6.0 and it's ok. feel free to close (as UPSTREAM??) thanks
