From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Hoyer, David" <David.Hoyer@netapp.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen supported LAPIC features
Date: Sat, 26 Oct 2013 01:19:23 +0100 [thread overview]
Message-ID: <526B0A8B.3050303@citrix.com> (raw)
In-Reply-To: <6777CD901FD53644B082307CD745FB8326A048FD@SACEXCMBX02-PRD.hq.netapp.com>
On 25/10/2013 20:45, Hoyer, David wrote:
> I wanted to follow up on this discussion just so that the community knows what I have discovered.
>
> Previously I was running with Xen 4.2.2/Debian(sid) and vxWorks 6.9.3 and was having the problems previously described. Based on some feedback, I decided to upgrade to vxWorks 6.9.3.2 (their latest) and ran into some new yet different problems. I debugged it down to an issue with how they were terminating early in the MP table scan if the MP tables did not have certain information in it. When I removed the early termination and allowed it to resume in spite of this particular data being missing, it suddenly was able to boot up successfully using the loapic timer! I am also no longer getting the error message that Andrew pointed out earlier.
>
> Thanks for the help, Andrew.
Thats good news that you have managed to make it work.
Which information is vxWorks expecting from the MP tables which is not
present? If it is useful information then we might as well be
presenting it.
~Andrew
next prev parent reply other threads:[~2013-10-26 0:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 19:03 Xen supported LAPIC features Hoyer, David
2013-10-08 19:12 ` Andrew Cooper
2013-10-08 19:37 ` Hoyer, David
2013-10-08 20:33 ` Andrew Cooper
2013-10-09 14:04 ` Hoyer, David
2013-10-09 14:11 ` Andrew Cooper
2013-10-09 15:55 ` Hoyer, David
2013-10-25 19:45 ` Hoyer, David
2013-10-26 0:19 ` Andrew Cooper [this message]
2013-10-26 14:36 ` Hoyer, David
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=526B0A8B.3050303@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=David.Hoyer@netapp.com \
--cc=xen-devel@lists.xen.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).