From: Jason Andryuk <jandryuk@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Aaron Janse <aaron@ajanse.me>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [BUG] panic: "IO-APIC + timer doesn't work" - several people have reproduced
Date: Tue, 17 Mar 2020 12:31:51 -0400 [thread overview]
Message-ID: <CAKf6xpv+wBRG-5ML-24O08gbs+hMFgyJKttV7KK7cx8i3smECw@mail.gmail.com> (raw)
In-Reply-To: <20200317152310.114567-1-jandryuk@gmail.com>
On Tue, Mar 17, 2020 at 11:23 AM Jason Andryuk <jandryuk@gmail.com> wrote:
>
> On 17.03.2020 15:08, Jan Beulich wrote:
> >On 17.03.2020 15:08, Jan Beulich wrote:
> >> On 17.03.2020 14:48, Jason Andryuk wrote:
> >>> I got it to boot past "IO-APIC + timer doesn't work". I programmed
> >>> the HPET to provide a periodic timer in hpet_resume() on T0. When I
> >>> actually got it programmed properly, it worked to increment
> >>> pit0_ticks. I also made timer_interrupt() unconditionally
> >>> pit0_ticks++ though that may not matter.
> >>
> >> Hmm, at the first glance I would imply the system gets handed to Xen
> >> with a HPET state that we don't (and probably also shouldn't) expect.
> >> Could you provide HPET_CFG as well as all HPET_Tn_CFG and
> >> HPET_Tn_ROUTE values as hpet_resume() finds them before doing any
> >> adjustments to them? What are the components / parties involved in
> >> getting Xen loaded and started?
I forgot to mention the boot sequence:
EFI -> grub2-efi -> xen.gz
grub2 is using multiboot2 & module2 commands.
Thanks for taking a look.
Regards,
Jason
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-03-17 16:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 7:52 [Xen-devel] [BUG] panic: "IO-APIC + timer doesn't work" - several people have reproduced Aaron Janse
2019-12-31 8:27 ` Andrew Cooper
2019-12-31 9:07 ` Aaron Janse
2020-02-17 19:19 ` Jason Andryuk
2020-02-17 19:46 ` Andrew Cooper
2020-02-17 20:41 ` Jason Andryuk
2020-02-18 1:21 ` Andrew Cooper
2020-02-18 18:43 ` Jason Andryuk
2020-02-18 21:45 ` Andrew Cooper
2020-02-19 8:25 ` Jan Beulich
2020-03-04 16:06 ` Jason Andryuk
2020-03-17 13:48 ` Jason Andryuk
2020-03-17 14:08 ` Jason Andryuk
2020-03-17 14:17 ` Jan Beulich
2020-03-17 14:08 ` Jan Beulich
2020-03-17 14:15 ` Jan Beulich
2020-03-17 15:23 ` Jason Andryuk
2020-03-17 16:31 ` Jason Andryuk [this message]
2020-03-18 10:28 ` Jan Beulich
2020-03-18 14:04 ` Jason Andryuk
2020-03-18 17:34 ` Jason Andryuk
2020-04-17 9:31 ` Jan Beulich
2020-04-28 20:59 ` Jason Andryuk
2020-03-04 16:05 ` Jason Andryuk
2020-01-03 12:51 ` Jan Beulich
2020-01-06 0:35 ` Aaron Janse
2020-01-06 8:57 ` Jan Beulich
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=CAKf6xpv+wBRG-5ML-24O08gbs+hMFgyJKttV7KK7cx8i3smECw@mail.gmail.com \
--to=jandryuk@gmail.com \
--cc=aaron@ajanse.me \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.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).