Re: 2.6.8.1-mm2 breaks vmware

[Ville Herva <vherva@viasys.com>]

On Fri, Aug 20, 2004 at 11:45:18AM -0700, you [Andrew Morton] wrote:
> > 
> >  --8<-----------------------------------------------------------------------
> >  vmmon: Your kernel is br0ken. get_user_pages(current, current->mm, b7dd1000, 1, 1, 0, &page, NULL) returned -14.
> >  vmmon: I'll try accessing page tables directly, but you should know that your
> >  vmmon: kernel is br0ken and you should uninstall all additional patches you vmmon: have installed!
> >  vmmon: FYI, copy_from_user(b7dd1000) returns 0 (if not 0 maybe your kernel is not br0ken)
> >  --8<-----------------------------------------------------------------------
> > 
> >  warning, but vmware appears to work now (well apart from altgr not working,
> >  but that has been broken since 2.4 -> 2.6 transition.)
> > 
> >  I'm still not 100% which of the patches causes that get_user_pages()
> >  warning.
> 
> If you could work that out sometime, it would help.

* 2.6.8.1-mm2 minus just dev-mem-restriction-patch.patch fixes the "cannot
  allocate memory" problem.

* 2.6.8.1-mm2 minus dev-mem-restriction-patch.patch and
  get_user_pages-handle-VM_IO.patch fixes both the "cannot allocate memory"
  and "get_user_pages() returns -EFAULT" problems.

"Cannot allocate memory" may be specific to older vmware 3.2.0 since it
hasn't been reported by anyone else (even though the patch is present in
Fedora). 



-- v -- 

v@iki.fi