From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IO_APIC NMI Watchdog not handled by suspend/resume.
Date: Fri, 12 Nov 2004 07:24:01 +1100 [thread overview]
Message-ID: <1100204641.4579.2.camel@desktop.cunninghams> (raw)
In-Reply-To: <20041110233045.GB1099@elf.ucw.cz>
Hi.
On Thu, 2004-11-11 at 10:30, Pavel Machek wrote:
> Hi!
>
> > Tracking down SMP problems, I've found that if you boot with
> > nmi_watchdog=1 (IO_APIC), the watchdog continues to run while suspend is
> > doing sensitive things like restoring the original kernel. I don't know
> > enough to provide a patch to disable it so thought I'd ask if someone
> > could volunteer to fix this?
>
> When we debated this at x86-64 lists, our conclusion was 'critical
> section should take less than 5 seconds, and watchdog only touches its
> own variables, so stopping it should not be needed'. [on x86-64,
> watchdog is enabled even on up].
I've since decided this too; it turns out that the SMP problems were a
function of a problem with freezing workthreads, which I've since fixed.
I have a perfectly stable system now. Which reminds me, since that code
was merged, I should send the patch to Andy. Will do so shortly.
Regards,
Nigel
--
Nigel Cunningham
Pastoral Worker
Christian Reformed Church of Tuggeranong
PO Box 1004, Tuggeranong, ACT 2901
You see, at just the right time, when we were still powerless, Christ
died for the ungodly. -- Romans 5:6
next prev parent reply other threads:[~2004-11-11 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 8:33 IO_APIC NMI Watchdog not handled by suspend/resume Nigel Cunningham
2004-11-05 16:41 ` Zwane Mwaikambo
2004-11-05 21:17 ` Nigel Cunningham
2004-11-06 9:50 ` Nigel Cunningham
2004-11-10 23:30 ` Pavel Machek
2004-11-11 20:24 ` Nigel Cunningham [this message]
2004-11-12 1:13 ` Zwane Mwaikambo
2004-11-11 20:32 ` Nigel Cunningham
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=1100204641.4579.2.camel@desktop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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