mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yoshihiro Takahashi <ytakahashi@miraclelinux.com>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Huang Ying <ying.huang@intel.com>,
	kexec@lists.infradead.org, Bernhard Walle <bwalle@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kdump hangs up by Sysrq+C trigger in high load.
Date: Tue, 16 Dec 2008 12:09:49 +0100	[thread overview]
Message-ID: <20081216110949.GB4299@elte.hu> (raw)
In-Reply-To: <20081216152143.88caba51.ytakahashi@miraclelinux.com>


* Yoshihiro Takahashi <ytakahashi@miraclelinux.com> wrote:

> Hi.
> 
> kdump hangs up by Sysrq+C trigger once in about 10 times in high load. 
> After the above occurs, kdump cannot collect vmcores with NMI button. 
> When waiting_for_crash_ipi does case more than 0, mdelay seem to make a 
> stall.
> 
> While nmi_shootdown_cpus(), mdelay may not work since interruption is 
> disable.  (ex. when crashing kernel by NMI interruption, all 
> interruption may be disabled.).
> 
> So I think that it should use other way (TSC) instead of mdelay() in 
> nmi_shootdown_cpus().

mdelay uses either the tsc or CPU loops - neither stop while IRQs are 
disabled.

Could you figure out exactly why it hangs in your case?

	Ingo

  reply	other threads:[~2008-12-16 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16  6:21 Yoshihiro Takahashi
2008-12-16 11:09 ` Ingo Molnar [this message]
2008-12-17  7:42   ` Yoshihiro Takahashi

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=20081216110949.GB4299@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=bwalle@suse.de \
    --cc=ehabkost@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=ying.huang@intel.com \
    --cc=ytakahashi@miraclelinux.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

all inboxes | Powered by JetHome®