From: Andi Kleen <ak@suse.de>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Andrew Morton <akpm@osdl.org>, virtualization@lists.osdl.org
Subject: Re: [PATCH 1/5] Skip timer works.patch
Date: Thu, 16 Nov 2006 20:46:04 +0100 [thread overview]
Message-ID: <200611162046.04264.ak@suse.de> (raw)
In-Reply-To: <20061116190334.GF1397@sequoia.sous-sol.org>
On Thursday 16 November 2006 20:03, Chris Wright wrote:
> * Andi Kleen (ak@suse.de) wrote:
> > I merged everything together. Synced out to ff now.
>
> OK, thanks.
>
> > CONFIG_PARAVIRT=n kernel runs now, but when I run a defconfig + CONFIG_PARAVIRT=y
> > kernel on bare metal init still breaks with a long stream of
> >
> > INIT: Entering runlevel: 3
> > Inconsistency detected by ld.so: rtld.c: 1250: dl_main: Assertion `(void *) ph->
> > p_vaddr == _rtld_local._dl_sysinfo_dso' failed!
> > Inconsistency detected by ld.so: rtld.c: 1250: dl_main: Assertion `(void *) ph->
> > p_vaddr == _rtld_local._dl_sysinfo_dso' failed!
> > Inconsistency detected by ld.so: rtld.c: 1250: dl_main: Assertion `(void *) ph->
> > p_vaddr == _rtld_local._dl_sysinfo_dso' failed!
> > Inconsistency detected by ld.so: rtld.c: 1250: dl_main: Assertion `(void *) ph->
> > p_vaddr == _rtld_local._dl_sysinfo_dso' failed!
> > ...
> >
> > before giving up. So it looks like something is still broken
>
> Another one that was working here. I'll debug with your config.
I started some bisecting (it's difficult because many intermediaries
don't compile -- something to clean up). Anyways, for this order of
paravirt patches:
header-and-stubs-for-paravirtualisation
patch-inline-replacements-for
paravirt-compile
cpu_detect-extraction
more-generic-paravirtualization
allow-selected-bug-checks-to-be
allow-disabling-legacy-power
add-apic-accessors-to-paravirt-ops.
add-mmu-virtualization-to
be-careful-about-touching-bios-address-space
mmu-header-movement
fix-bad-mmu-names
fix-missing-pte-update
fix-x86_64-mm-patch-inline-replacements-for
paravirt-pae
skip-timer-works
it's already broken at more-generic-paravirtualization. Surprised
me a little, i was suspecting the MMU changes.
-Andi
next prev parent reply other threads:[~2006-11-16 19:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 0:09 [PATCH 1/5] Skip timer works.patch Zachary Amsden
2006-10-27 14:56 ` Andi Kleen
2006-10-27 19:09 ` Zachary Amsden
2006-10-27 21:16 ` Andi Kleen
2006-10-30 20:54 ` Zachary Amsden
2006-10-30 22:50 ` Andi Kleen
2006-10-30 23:09 ` Zachary Amsden
2006-10-30 23:12 ` Andi Kleen
2006-10-30 23:24 ` Zachary Amsden
2006-10-30 23:50 ` Andi Kleen
2006-11-15 8:03 ` Chris Wright
2006-11-15 8:21 ` Zachary Amsden
2006-11-15 22:40 ` Chris Wright
2006-11-15 22:54 ` Chris Wright
2006-11-16 3:27 ` Andi Kleen
2006-11-16 3:37 ` Chris Wright
2006-11-16 3:37 ` Andi Kleen
2006-11-16 5:06 ` Andrew Morton
2006-11-16 6:13 ` Zachary Amsden
2006-11-16 7:23 ` Andi Kleen
2006-11-16 7:02 ` Andi Kleen
2006-11-16 7:16 ` Chris Wright
2006-11-16 8:26 ` Chris Wright
2006-11-16 10:28 ` Chris Wright
2006-11-16 13:16 ` Andi Kleen
2006-11-16 19:03 ` Chris Wright
2006-11-16 19:46 ` Andi Kleen [this message]
2006-11-16 20:24 ` Chris Wright
2006-11-17 4:47 ` Andi Kleen
2006-11-17 7:33 ` Chris Wright
2006-11-17 7:38 ` Andi Kleen
2006-11-16 22:53 ` Andrew Morton
2006-11-16 23:08 ` Zachary Amsden
2006-11-16 23:10 ` Chris Wright
2006-11-17 5:05 ` Andi Kleen
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=200611162046.04264.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.org \
/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;
as well as URLs for NNTP newsgroup(s).