From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758190AbYGJOwq (ORCPT ); Thu, 10 Jul 2008 10:52:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757283AbYGJOwh (ORCPT ); Thu, 10 Jul 2008 10:52:37 -0400 Received: from mx2.suse.de ([195.135.220.15]:52539 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755631AbYGJOwg (ORCPT ); Thu, 10 Jul 2008 10:52:36 -0400 Date: Fri, 11 Jul 2008 04:52:29 +0200 Message-ID: From: Takashi Iwai To: Jeremy Fitzhardinge Cc: Ingo Molnar , LKML Subject: Re: next-0710: CONFIG_PARAVIRT broken on x86_64? In-Reply-To: <487621BC.4040001@goop.org> References: <487621BC.4040001@goop.org> 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: X-Mailing-List: linux-kernel@vger.kernel.org At Thu, 10 Jul 2008 07:50:36 -0700, Jeremy Fitzhardinge wrote: > > Takashi Iwai wrote: > > Hi, > > > > does paravirt work on x86_64 with the recent linux-next kernels? > > I have a boot problem, a segfault of init at the very beginning. > > > > Freeing memory ... > > init[1]: segfault ... in libc-2.8.so > > > > The backtrace is like below: > > ? do_coredump > > ? blocking_notifier_call_chain > > do_exit > > do_group_exit > > get_signal_to_deliver > > do_notify_resume > > ? do_wait > > ? default_wake_function > > retint_signal > > > > The kconfig is below. When I set CONFIG_PARAVIRT=n, it works fine. > > > > The problem exists at least since 20080703 until today, maybe in the > > earlier versions, too. The similar config works on i386. > > > > Is your userspace 32 or 64 bit? 64bit. Takashi