From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1756796AbYGNQzW@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1756796AbYGNQzW (ORCPT <rfc822;w@1wt.eu>);
	Mon, 14 Jul 2008 12:55:22 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753916AbYGNQzK
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 14 Jul 2008 12:55:10 -0400
Received: from cantor.suse.de ([195.135.220.2]:52938 "EHLO mx1.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753068AbYGNQzI (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 14 Jul 2008 12:55:08 -0400
Date: Wed, 16 Jul 2008 04:54:49 +0200
Message-ID: <s5hod4ywnba.wl%tiwai@suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: next-0710: CONFIG_PARAVIRT broken on x86_64?
In-Reply-To: <s5hhcavxy3f.wl%tiwai@suse.de>
References: <s5htzexryqy.wl%tiwai@suse.de>
	<487621BC.4040001@goop.org>
	<s5hmykprv2q.wl%tiwai@suse.de>
	<48765CCD.4070308@goop.org>
	<s5hlk08rgv8.wl%tiwai@suse.de>
	<48766D17.9000704@goop.org>
	<s5hhcavxy3f.wl%tiwai@suse.de>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/22.2
 (x86_64-suse-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

At Sat, 12 Jul 2008 11:15:16 +0200,
I wrote:
> 
> At Thu, 10 Jul 2008 13:12:07 -0700,
> Jeremy Fitzhardinge wrote:
> > 
> > Takashi Iwai wrote:
> > > Native.  Booted on a HP machine with two Intel x86-64 CPUs.
> > >   
> > 
> > Is that the complete log of what it prints out?  Does it print any 
> > addresses or anything?
> >
> > Could you try tip.git with the config to see if its there?  I don't 
> > think there should be anything relevent in -next, but there could be a 
> > merge problem or something.
> 
> Almost same result.  The init segfaults at the very beginning.
> The below is the whole screen output I could copy by hand (may include
> some types).
> 
> > Does booting with "init=/bin/sh" make any progress?
> 
> No change.

This seems fixed on linux-next-20080714 magically.
Thanks for your help, anyway!


Takashi