All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: [PATCH] SMP dom0 boot fix
Date: Fri, 28 Oct 2005 16:15:12 +0100	[thread overview]
Message-ID: <db942d6187efc7983edf6dff41bc3dcd@cl.cam.ac.uk> (raw)
In-Reply-To: <20051028145930.GL22394@us.ibm.com>


On 28 Oct 2005, at 15:59, Ryan Harper wrote:

> At this point send_IPI_allbutself() has been invoked and the system
> just sits and waits on CPU1 to run the function.  But, CPU1's
> evtchn_upcall_mask was set (1), so I'm guessing the pending interrupt
> is never acknowledged.

Okay, the good news is that's the same bug I was able to repro last 
week. Turns out that CPU1's upcall mask is getting weirdly set under 
its feet. Since it's waiting on the big kernel lock, which is held by 
CPU0, which is waiting for acknowledgement of an interrupt in CPU1, we 
have a deadlock.

Given the problem is in that one changeset, this can't be hard to track 
down now.

  -- Keir

  reply	other threads:[~2005-10-28 15:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28  1:05 [PATCH] SMP dom0 boot fix Kamble, Nitin A
2005-10-28  7:31 ` Keir Fraser
2005-10-28 14:59   ` Ryan Harper
2005-10-28 15:15     ` Keir Fraser [this message]
2005-10-28 15:45       ` Keir Fraser
2005-10-28 16:07         ` Ryan Harper
2005-10-28 17:27         ` Ky Srinivasan
  -- strict thread matches above, loose matches on Subject: below --
2005-10-28 14:34 Puthiyaparambil, Aravindh
2005-10-28 17:13 Kamble, Nitin A
2005-10-28 23:52 Ian Pratt
2005-10-31 18:32 ` Ky Srinivasan
2005-10-31 18:32 ` Ky Srinivasan

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=db942d6187efc7983edf6dff41bc3dcd@cl.cam.ac.uk \
    --to=keir.fraser@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=ryanh@us.ibm.com \
    --cc=xen-devel@lists.xensource.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 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.