Bug#602418: linux-image-2.6.32-5-xen-amd64: with xen 4.0, fork()/clone() fails with ENOMEM during X startup with nv driver

To: Timo Juhani Lindfors <timo.lindfors@iki.fi>
Cc: 602418@bugs.debian.org
Subject: Bug#602418: linux-image-2.6.32-5-xen-amd64: with xen 4.0, fork()/clone() fails with ENOMEM during X startup with nv driver
From: Lionel Elie Mamane <lionel@mamane.lu>
Date: Thu, 18 Nov 2010 09:19:05 +0100
Message-id: <[🔎] 20101118081905.GC24367@capsaicin.mamane.lu>
Reply-to: Lionel Elie Mamane <lionel@mamane.lu>, 602418@bugs.debian.org
In-reply-to: <[🔎] 8462vvnkp0.fsf@sauna.l.org>
References: <[🔎] 8462vvnkp0.fsf@sauna.l.org>

On Thu, Nov 18, 2010 at 09:40:43AM +0200, Timo Juhani Lindfors wrote:

> Hmm. So you are running an X server in the dom0 or in a domU?

In the dom0.

-- 
Lionel

Reply to:

Follow-Ups:
- Bug#602418: linux-image-2.6.32-5-xen-amd64: with xen 4.0, fork()/clone() fails with ENOMEM during X startup with nv driver
  - From: Ian Campbell <ijc@hellion.org.uk>

References:
- Bug#602418: linux-image-2.6.32-5-xen-amd64: with xen 4.0, fork()/clone() fails with ENOMEM during X startup with nv driver
  - From: Timo Juhani Lindfors <timo.lindfors@iki.fi>

Prev by Date: Processed (with 1 errors): blank
Next by Date: Processed: blank
Previous by thread: Bug#602418: linux-image-2.6.32-5-xen-amd64: with xen 4.0, fork()/clone() fails with ENOMEM during X startup with nv driver
Next by thread: Bug#602418: linux-image-2.6.32-5-xen-amd64: with xen 4.0, fork()/clone() fails with ENOMEM during X startup with nv driver
Index(es):
- Date
- Thread