public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: XIAO Gang <xiao@unice.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: UML mode panick under 2.6.12
Date: Tue, 21 Jun 2005 09:03:19 -0400	[thread overview]
Message-ID: <20050621130319.GA4510@ccure.user-mode-linux.org> (raw)
In-Reply-To: <42B7C0FA.8070409@unice.fr>

On Tue, Jun 21, 2005 at 09:25:46AM +0200, XIAO Gang wrote:
> 
> I am unable to run UML mode (i386) under 2.6.12: the execution gives the 
> following messages.
> 
> ---------------------------------------------------------------------------------------------

> Checking that ptrace can change system call numbers...<0>Kernel panic - 
> not syncing: Segfault with no mm

Can you try backing out the use-fork-instead-of-clone patch?  Ben LaHaise
reported that caused problems for him.

				Jeff

  reply	other threads:[~2005-06-21 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21  7:25 UML mode panick under 2.6.12 XIAO Gang
2005-06-21 13:03 ` Jeff Dike [this message]
2005-06-21 14:09   ` XIAO Gang

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=20050621130319.GA4510@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiao@unice.fr \
    /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