From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <eee6d8a6737344d77badb04fe912033c@kw.quanstro.net>
References: <4C1242CD.5020202@bouyapop.org>
	<AANLkTin7gyORvSQewxdWAxwHdI6dlp0UTK6kHAjKKyt0@mail.gmail.com>
	<eee6d8a6737344d77badb04fe912033c@kw.quanstro.net>
Date: Fri, 11 Jun 2010 08:43:28 -0700
Message-ID: <AANLkTinuVr-f5uYeTvbWtQZoiCA_y-DVyWfHKpscRBfc@mail.gmail.com>
From: ron minnich <rminnich@gmail.com>
To: erik quanstrom <quanstro@quanstro.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: 9fans@9fans.net
Subject: Re: [9fans] 9vx, kproc and *double sleep*
Topicbox-Message-UUID: 319c71fa-ead6-11e9-9d60-3106f5b1d025

On Fri, Jun 11, 2010 at 8:04 AM, erik quanstrom <quanstro@quanstro.net> wro=
te:

> please wait. =A0we still don't understand this problem
> very well. =A0(why does this work on real hardware?)

all the 9vx failures I have seen are with the kexec threads. This is a
major 0vx change from 9. I do think that there is something in what
Phillipe is saying.

ron