Re: 2.6.8.1-mm2 breaks vmware

[Andrew Morton <akpm@osdl.org>]

Ville Herva <vherva@viasys.com> wrote:
>
>  On Fri, Aug 20, 2004 at 05:43:04PM +0300, you [Ville Herva] wrote:
>  > On Fri, Aug 20, 2004 at 04:18:25PM +0300, you [Ville Herva] wrote:
>  > > 
>  > > I just noticed I had missed get_user_pages-handle-VM_IO.patch - I'll try
>  > > backing that out first. I'll report back if I find anything interesting 
>  > > with different patch mixtures.
>  > 
>  > Well, I just tried 2.6.8.1-mm2 minus get_user_pages-handle-VM_IO.patch but
>  > that didn't help with the "cannot allocate memory" problem. Curiously, I
>  > didn't get the "get_user_pages() returns -EFAULT" warning with this kernel.
>  > 
>  > I just put get_user_pages-handle-VM_IO.patch back and reverted
>  > dev-mem-restriction-patch.patch - I'll report back when it has compiled. 
> 
>  Ok, 2.6.8.1-mm2 minus dev-mem-restriction-patch.patch fixes the "cannot
>  allocate memory" problem. 

Thanks for working that out.

Strange.  I'd have assumed that the Fedora kernels include that patch.

>  With this kernel I still get the 
> 
>  --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.