mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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?
Date: Wed, 16 Jul 2008 04:54:49 +0200	[thread overview]
Message-ID: <s5hod4ywnba.wl%tiwai@suse.de> (raw)
In-Reply-To: <s5hhcavxy3f.wl%tiwai@suse.de>

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

  reply	other threads:[~2008-07-14 16:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11  1:33 Takashi Iwai
2008-07-10 14:50 ` Jeremy Fitzhardinge
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 [this message]
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=s5hod4ywnba.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

all inboxes | Powered by JetHome®