126.96.36.199-mm2 breaks vmware
From: Ville Herva
Date: Fri Aug 20 2004 - 05:43:38 EST
Andrew, I know you are not interested in closed source vmware, I'm just
blatantly Cc'ing you in case you would have some suggestion of the top of
your head. As stuff slowly trickles from -mm to mainline, this could
eventually end up biting more people.
In short, there are two (afaict) separate problem:
(1) vmmon.ko gives this:
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)
(2) vmware fails to start any guest os, telling it cannot allocate memory:
VMX|[msg.msg.noMem] Cannot allocate memory.
(1) happened with 2.6.6-mm4 and with 188.8.131.52-mm2.
(2) only happened with 184.108.40.206-mm2 (with 2.6.6-mm4 vmware worked despite the
So I backed out these patches from 220.127.116.11-mm2:
(All conveniently available for reference at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/18.104.22.168/22.214.171.124-mm2/broken-out/
if anyone is interested)
I had a vague hunch that flex-mmap stuff might affect (2) and
get_user_pages patch perhaps (1).
After this, problem (1) went away for 126.96.36.199-mm2, but problem (2) remained.
Then I tried 188.8.131.52 vanilla. It does NOT suffer from either (1) or (2).
All experiments are done with Petr Vandrovec's newest
vmware-any-any-update81 (apart from 2.6.6-mm4 that had some older any-to-any
patch) and VMwareWorkstation-3.2.0-2230.
Before I continue backing stuff out: does anyone have ideas or suggestions
what -mm patches might be suspectible problem (2)? 184.108.40.206 -> 220.127.116.11-mm2 is
rather large patch and so is 2.6.6-mm4 -> 18.104.22.168-mm2, and the patches
listed above were everything I thought might be suspectible.
Could get_user_pages-latency-fix.patch explain (1)? My kernel expertise is
not sufficient to tell.
-- v --
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/