From: Ted Kaczmarek <tedkaz@optonline.net>
To: Jeremy Katz <katzj@redhat.com>
Cc: xen-devel@lists.xensource.com, Thomas Kofler <xen@kofler.eu.org>
Subject: Re: Kernel panic, Domain 0 shutdown (was Aieee! CPU0 is toast...)
Date: Thu, 01 Sep 2005 10:22:34 -0400 [thread overview]
Message-ID: <1125584554.2488.5.camel@inyoureyes.linsolutions.com> (raw)
In-Reply-To: <1125583520.2569.98.camel@bree.local.net>
On Thu, 2005-09-01 at 10:05 -0400, Jeremy Katz wrote:
> On Thu, 2005-09-01 at 14:47 +0200, Thomas Kofler wrote:
> > I upgraded to the latest FC4 rpms on this server and got the serial debug to
> > work. We did "mv /lib/tls /lib/tls.disabled" but the tls message also
> > remained, which was not the case with older rpms.
>
> This message is misleading and not actually the case with current Fedora
> glibc builds (including FC4). Xen triggers the use of
> the /lib/i686/nosegneg glibc binaries which don't really have the
> performance hits. Prior xen builds have had this message patched out,
> but the most recent build didn't have this done.
>
> Jeremy
>
>
> _______________________________________________
I had to append vdso=0 with those rpms on FC4 on my smp athlon to get it
to boot at all.
Also xen built rpm from
changeset: 6464:b3785cbb723b8b355c1282232de0bd1cfbfb3556
tag: tip
user: cl349@firebug.cl.cam.ac.uk
date: Mon Aug 29 18:40:47 2005
summary: Simplify and fix SMP irq and ipi teardown/setup on
suspend/resume.
to get xend to play nicer, the xen-2-20050823 was brutal :-)
Having issue with xen_net but that may be specific to my hardware, tyan
2462.
Not sure if it helps but I would definitely try passing vdso=0
Regards,
Ted
next prev parent reply other threads:[~2005-09-01 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 12:47 Kernel panic, Domain 0 shutdown (was Aieee! CPU0 is toast...) Thomas Kofler
2005-09-01 14:05 ` Jeremy Katz
2005-09-01 14:22 ` Ted Kaczmarek [this message]
2005-09-02 8:05 ` Thomas Kofler
-- strict thread matches above, loose matches on Subject: below --
2005-09-01 12:48 Petersson, Mats
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=1125584554.2488.5.camel@inyoureyes.linsolutions.com \
--to=tedkaz@optonline.net \
--cc=katzj@redhat.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen@kofler.eu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.