From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
Ian Campbell <Ian.Campbell@XenSource.com>
Subject: Re: Xen status
Date: Wed, 13 Sep 2006 23:35:59 -0700 [thread overview]
Message-ID: <4508F84F.2060802@goop.org> (raw)
In-Reply-To: <20060914015915.GP10348@sequoia.sous-sol.org>
Chris Wright wrote:
>> With these in place, things are getting fairly far, but not to
>> usermode. It often gets as far as trying to mount root, but it fails; I
>> haven't investigated that yet. But it also frequently crashes before
>> then, depending on when it gets an interrupt. I'm trying to work out
>> what's happening here, but the symptom is eip == 0x00000001 (!).
>>
>
> Haven't seen that one.
>
Yeah, it looks like something is going amiss in interrupt delivery.
Maybe something to do with interrupt stacks...
I never saw anything strange relating to timer events, but perhaps this
is a manifestation of that problem.
> Essentially all the local hacks I have are for debugging. There was
> one bit which was just for apic clock setup.
I think I worked around that by masking off the ACPI bit in CPUID.
> But the symptom w/out that was a hang, not a crash.
Yes, I'm past that one.
> They're also on a remote machine that
> has apparently died. Re-tooling locally ATM.
>
That sucks.
J
prev parent reply other threads:[~2006-09-14 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 22:58 Xen status Jeremy Fitzhardinge
2006-09-14 0:30 ` Zachary Amsden
2006-09-14 1:59 ` Chris Wright
2006-09-14 6:35 ` Jeremy Fitzhardinge [this message]
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=4508F84F.2060802@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@XenSource.com \
--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 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.