From: Ville Herva <vherva@viasys.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
petr@vandrovec.name, linux-kernel@vger.kernel.org
Subject: Re: 2.6.8.1-mm2 breaks vmware
Date: Fri, 20 Aug 2004 22:30:24 +0300 [thread overview]
Message-ID: <20040820193024.GL23741@viasys.com> (raw)
In-Reply-To: <20040820184932.GA11789@devserv.devel.redhat.com>
On Fri, Aug 20, 2004 at 08:49:33PM +0200, you [Arjan van de Ven] wrote:
> > >
> > > 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.
>
> we do. Maybe you have an older (rare) vmware version ???
Yes, VMwareWorkstation-3.2.0-2230.
Looks like I'll need to break my piggy bank and consider upgrading.
Commercial software... ;@)
-- v --
v@iki.fi
next prev parent reply other threads:[~2004-08-20 19:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 10:42 2.6.8.1-mm2 breaks vmware Ville Herva
2004-08-20 10:51 ` Andrew Morton
2004-08-20 13:18 ` Ville Herva
2004-08-20 14:43 ` Ville Herva
2004-08-20 15:16 ` Ville Herva
2004-08-20 18:45 ` Andrew Morton
2004-08-20 18:49 ` Arjan van de Ven
2004-08-20 19:30 ` Ville Herva [this message]
2004-08-22 11:42 ` Tonnerre
2004-08-22 13:59 ` Petr Vandrovec
2004-08-22 14:15 ` Alan Cox
2004-08-20 19:25 ` Ville Herva
2004-08-21 6:29 ` Ville Herva
[not found] ` <20040821134918.GA1585@devserv.devel.redhat.com>
[not found] ` <20040821190027.GQ3024@viasys.com>
[not found] ` <20040821190730.GA25932@devserv.devel.redhat.com>
2004-08-22 14:31 ` Petr Vandrovec
2004-08-22 15:07 ` Arjan van de Ven
2004-08-22 21:19 ` Ville Herva
2004-08-23 5:53 ` [OT] vmware, 2.6 kernel and altgr key (Re: 2.6.8.1-mm2 breaks vmware) Ville Herva
2004-08-20 12:11 ` 2.6.8.1-mm2 breaks vmware Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040820193024.GL23741@viasys.com \
--to=vherva@viasys.com \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@vandrovec.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox