I know this probably doesn't fix your problem, but there's a program called QEMU that might perform similar functionality to VMWare; does it have the same issues? Maybe you want to try that, and see if you have the same problem or not...
On 8/28/05, Ronald Moesbergen <[EMAIL PROTECTED]> wrote: > OK, but the tainting is because the license is different from GPL, not > because of lack of source code (vmware modules source code is > available). Anyway, I'll wait for a fix. Let me know if there's > anything I can do to help. > > Ronald. > > On 8/28/05, evilninja <[EMAIL PROTECTED]> wrote: > > Ronald Moesbergen schrieb: > > > Well, I just successfully reproduced this without the nvidia module > > > loaded. The oops looks very similar: > > [...] > > > kernel: Modules linked in: vmnet vmmon > > > kernel: CPU: 1 > > > kernel: EIP: 0060:[lock_object+84/127] Tainted: P VLI > > > > well, the kernel is still tainted - by the vmware modules. but as Vladimir > > pointed out, there seem to be vmware related issues in reiser4. so you > > could wait for the fix or try to reproduce with an untainted kernel (maybe > > it's a completly different problem which needs to be fixed). > > > > Christian. > > -- > > BOFH excuse #432: > > > > Borg nanites have infested the server > > > -- ~Mike - Just my two cents - No man is an island, and no man is unable.
