All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML woes in 2.6.24-rc6-mm1
Date: Wed, 2 Jan 2008 15:06:21 -0500	[thread overview]
Message-ID: <20080102200621.GB8847@c2.user-mode-linux.org> (raw)
In-Reply-To: <E1JA7m0-0007nP-Fi@pomaz-ex.szeredi.hu>

On Wed, Jan 02, 2008 at 06:53:00PM +0100, Miklos Szeredi wrote:
> The below patch was needed to make UML compile in latest -mm.

ACK on that - I've got the same patch on its way.

> But sometimes it doesn't boot and does weird things (this is a sample
> with init=/bin/bash):

> (none):/# ls
> Segmentation fault
> (none):/# ls -l
> : : No such file or directory

Huh.  No problems here - I've got rc6-mm1 happily doing kernel builds.

Is this 32 or 64-bit?

Can you double-check that you have a clean pool and a clean build, etc?

				Jeff

-- 
Work email - jdike at linux dot intel dot com

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jeff Dike <jdike@addtoit.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML woes in 2.6.24-rc6-mm1
Date: Wed, 2 Jan 2008 15:06:21 -0500	[thread overview]
Message-ID: <20080102200621.GB8847@c2.user-mode-linux.org> (raw)
In-Reply-To: <E1JA7m0-0007nP-Fi@pomaz-ex.szeredi.hu>

On Wed, Jan 02, 2008 at 06:53:00PM +0100, Miklos Szeredi wrote:
> The below patch was needed to make UML compile in latest -mm.

ACK on that - I've got the same patch on its way.

> But sometimes it doesn't boot and does weird things (this is a sample
> with init=/bin/bash):

> (none):/# ls
> Segmentation fault
> (none):/# ls -l
> : : No such file or directory

Huh.  No problems here - I've got rc6-mm1 happily doing kernel builds.

Is this 32 or 64-bit?

Can you double-check that you have a clean pool and a clean build, etc?

				Jeff

-- 
Work email - jdike at linux dot intel dot com

  reply	other threads:[~2008-01-02 20:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 17:53 [uml-devel] UML woes in 2.6.24-rc6-mm1 Miklos Szeredi
2008-01-02 17:53 ` Miklos Szeredi
2008-01-02 20:06 ` Jeff Dike [this message]
2008-01-02 20:06   ` [uml-devel] " Jeff Dike
2008-01-02 20:52   ` Miklos Szeredi
2008-01-02 20:52     ` Miklos Szeredi
2008-01-02 22:05     ` Jeff Dike
2008-01-02 22:05       ` Jeff Dike
2008-01-03 12:55       ` Miklos Szeredi
2008-01-03 12:55         ` Miklos Szeredi
2008-01-04 18:00         ` Jeff Dike
2008-01-04 18:00           ` Jeff Dike
2008-01-04 19:53           ` Miklos Szeredi
2008-01-04 19:53             ` Miklos Szeredi

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=20080102200621.GB8847@c2.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.