From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerry Reno Subject: Re: 2.6.37 dom0 non-fatal BUG: sleeping function called from invalid context at kernel/mutex.c:85 Date: Thu, 06 Jan 2011 13:12:26 -0500 Message-ID: <4D26060A.9070002@verizon.net> References: <900599.56710.qm@web56105.mail.re3.yahoo.com> <4D2600D8.9020903@verizon.net> <20110106180019.GM2754@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-reply-to: <20110106180019.GM2754@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 01/06/2011 01:00 PM, Pasi K=E4rkk=E4inen wrote: > On Thu, Jan 06, 2011 at 12:50:16PM -0500, Gerry Reno wrote: > =20 >> On 01/06/2011 12:42 PM, Boris Derzhavets wrote: >> =20 >>> In response to Michael Young post fedora-xen list :- >>> >>> =20 >>>> There is a 2.6.37 kernel to test (2.6.37-1.xendom0.fc15) >>>> =20 >>> Works for me under Xen 4.0.1 , but attempt to "startx" causes stack t= race. >>> Works as vanilla as well . Allows to run KVMs been built with standar= d >>> fedora kernel. >>> >>> Boris. >>> >>> =20 >> Haven't tried 2.6.37 yet but I have not been able to get X running wit= h >> any of the dom0 kernels while using Ubuntu Lucid. I've always gotten = a >> stack trace. >> >> =20 > Which kernels did you try? > Can you post the stack trace?=20 > > -- Pasi > =20 I'm using this machine currently so I can't reboot it to get a stack trace. Too much work open. It's probably the same stack trace that Boris got. I tested using some 2.6.31 and 2.6.32 kernels. -Gerry