linux-kernel - Re: next-0710: CONFIG_PARAVIRT broken on x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hod4ywnba.wl%tiwai@suse.de>
Date:	Wed, 16 Jul 2008 04:54:49 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: next-0710: CONFIG_PARAVIRT broken on x86_64?

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/