public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: next-0710: CONFIG_PARAVIRT broken on x86_64?
Date: Thu, 10 Jul 2008 07:50:36 -0700	[thread overview]
Message-ID: <487621BC.4040001@goop.org> (raw)
In-Reply-To: <s5htzexryqy.wl%tiwai@suse.de>

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?

    J

  reply	other threads:[~2008-07-10 14:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11  1:33 next-0710: CONFIG_PARAVIRT broken on x86_64? Takashi Iwai
2008-07-10 14:50 ` Jeremy Fitzhardinge [this message]
2008-07-11  2:52   ` Takashi Iwai
2008-07-10 19:02     ` Jeremy Fitzhardinge
2008-07-11  7:59       ` Takashi Iwai
2008-07-10 20:12         ` Jeremy Fitzhardinge
2008-07-12  9:15           ` Takashi Iwai
2008-07-16  2:54             ` Takashi Iwai
2008-07-14 17:20               ` Jeremy Fitzhardinge

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=487621BC.4040001@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tiwai@suse.de \
    /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