From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757182AbYGJUMb (ORCPT ); Thu, 10 Jul 2008 16:12:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755798AbYGJUMU (ORCPT ); Thu, 10 Jul 2008 16:12:20 -0400 Received: from gw.goop.org ([64.81.55.164]:33233 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755795AbYGJUMU (ORCPT ); Thu, 10 Jul 2008 16:12:20 -0400 Message-ID: <48766D17.9000704@goop.org> Date: Thu, 10 Jul 2008 13:12:07 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Takashi Iwai CC: Ingo Molnar , LKML Subject: Re: next-0710: CONFIG_PARAVIRT broken on x86_64? References: <487621BC.4040001@goop.org> <48765CCD.4070308@goop.org> In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Does booting with "init=/bin/sh" make any progress? J