Summary: | vmware 5.5.3 modules make kernel oops and reboot machines | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrizio Bassi <patrizio.bassi> |
Component: | New packages | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Patrizio Bassi
2007-01-22 13:28:54 UTC
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 |