All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen-unstable: Regression (on AMD) host boot stuck on (XEN) testing the IO APIC.......................
Date: Tue, 26 Aug 2014 08:34:30 +0100	[thread overview]
Message-ID: <53FC54A6020000780002D776@mail.emea.novell.com> (raw)
In-Reply-To: <1283801136.20140825202522@eikelenboom.it>

>>> On 25.08.14 at 20:25, <linux@eikelenboom.it> wrote:
> Monday, August 25, 2014, 7:54:05 PM, you wrote:
>> Hmm - Does reverting e13b3203990706db1313ec2aadd9a30b249ee793 fix the issue?
> 
> Hmm i completely overlooked that commit (it's quite evident when you look at 
> the 
> commitdiff :-) )
> 
> Just tested reverting that single commit and that indeed lets the machine 
> boot again.

Considering how early this is, the only theory I have is that
rcu_pending() may end up constantly returning true, thus always
causing RCU_SOFTIRQ to get raised, not allowing the loop in
__do_softirq() to ever exit. If that's the case, we seem to have
two options:
- pass into __print_IO_APIC() whether it's being called from a key
  handler
- only call process_pending_softirqs() when system_state >=
  SYS_STATE_smp_boot

Personally I'd prefer the former option.

But Sander, a fundamental question: Why would you _always_
boot your system with "apic=debug" and those various other
debugging options? They are, as you may guess, for debugging,
not for day to day use. (That said I'm glad you have this in place
for this particular case, as it allowed spotting a regression early.)

Jan

  reply	other threads:[~2014-08-26  7:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-25 17:12 Xen-unstable: Regression (on AMD) host boot stuck on (XEN) testing the IO APIC Sander Eikelenboom
2014-08-25 17:54 ` Andrew Cooper
2014-08-25 18:25   ` Sander Eikelenboom
2014-08-26  7:34     ` Jan Beulich [this message]
2014-08-26  7:45       ` Jan Beulich
2014-08-26  9:32         ` Andrew Cooper
2014-08-26 10:29           ` Sander Eikelenboom
2014-08-26  9:00       ` Sander Eikelenboom

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=53FC54A6020000780002D776@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=linux@eikelenboom.it \
    --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 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.