[lkml]   [2004]   [Aug]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: breaks vmware
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 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, minus dev-mem-restriction-patch.patch fixes the "cannot
allocate memory" problem.

With this kernel I still get the

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)

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()

-- v --

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:05    [W:0.047 / U:1.136 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site