From: Thomas Gleixner <tglx@linutronix.de>
To: Michael Thayer <michael.thayer@oracle.com>
Cc: Michal Necasek <michal.necasek@oracle.com>,
prarit@redhat.com, ville.syrjala@linux.intel.com,
frank.mehnert@oracle.com, knut.osmundsen@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: 4.8.2 not booting in 32-bit VM without I/O-APIC
Date: Thu, 10 Nov 2016 18:18:29 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1611101817420.3501@nanos> (raw)
In-Reply-To: <9d85a95e-332c-db85-8e62-2015de8ecb85@oracle.com>
On Thu, 10 Nov 2016, Michael Thayer wrote:
> On 03.11.2016 21:02, Michal Necasek wrote:
> > Sorry for the delay. I can confirm that the problem is fixed in
> > 4.9.0-rc3 and prefill_possible_map no longer crashes (as it did in
> > 4.9.0-rc2). Thank you!
> >
> > Just a side question, is the previous fix in commit ff8560512b
> > (x86/boot/smp: Don't try to poke disabled/non-existent APIC) actually
> > still required or would the no-op APIC driver take care of it?
>
> Sorry for the delay too (holiday-related). I tested 4.9.0rc4 on a 32-bit
No problem. I hope you enjoyed your well earned vacation :)
> VirtualBox virtual machine without I/O-APIC and can confirm that it now boots.
> Since I am at it, the OHCI timer wheel-related problems are also no longer
> reproducible.
Thanks for reporting back!
tglx
next prev parent reply other threads:[~2016-11-10 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 20:02 4.8.2 not booting in 32-bit VM without I/O-APIC Michal Necasek
2016-11-10 14:21 ` Michael Thayer
2016-11-10 17:18 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-28 18:52 Michal Necasek
2016-10-28 19:00 ` Thomas Gleixner
2016-10-28 19:34 ` Thomas Gleixner
2016-10-29 10:18 ` Borislav Petkov
2016-10-28 18:30 Michal Necasek
2016-10-28 18:38 ` Thomas Gleixner
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=alpine.DEB.2.20.1611101817420.3501@nanos \
--to=tglx@linutronix.de \
--cc=frank.mehnert@oracle.com \
--cc=knut.osmundsen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.thayer@oracle.com \
--cc=michal.necasek@oracle.com \
--cc=prarit@redhat.com \
--cc=ville.syrjala@linux.intel.com \
/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).