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: <s5hlk08rgv8.wl%tiwai@suse.de>
Date:	Fri, 11 Jul 2008 09:59:23 +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 Thu, 10 Jul 2008 12:02:37 -0700,
Jeremy Fitzhardinge wrote:
> 
> Takashi Iwai wrote:
> > 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.
> >   
> 
> Booting native or under kvm?

Native.  Booted on a HP machine with two Intel x86-64 CPUs.


thanks,

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/