From: "David S. Miller" <davem@davemloft.net>
To: ak@suse.de
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: softlockup interaction with slow consoles
Date: Tue, 21 Feb 2006 12:19:48 -0800 (PST) [thread overview]
Message-ID: <20060221.121948.60060362.davem@davemloft.net> (raw)
In-Reply-To: <200602212105.38075.ak@suse.de>
From: Andi Kleen <ak@suse.de>
Date: Tue, 21 Feb 2006 21:05:37 +0100
> The classic way is to just use touch_nmi_watchdog() somewhere
> in the loop that does work. That touches the softwatchdog too
> these days.
"jiffies" aren't advancing, since interrupts are disabled by
release_console_sem(), so that doesn't work.
I tried that already :-)
next prev parent reply other threads:[~2006-02-21 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 21:18 softlockup interaction with slow consoles David S. Miller
2006-02-21 9:09 ` Ingo Molnar
2006-02-21 9:16 ` David S. Miller
2006-02-21 13:49 ` Andi Kleen
2006-02-21 20:01 ` David S. Miller
2006-02-21 20:05 ` Andi Kleen
2006-02-21 20:19 ` David S. Miller [this message]
2006-02-21 20:27 ` Dave Jones
2006-02-21 20:50 ` David S. Miller
2006-02-21 20:43 ` Andi Kleen
2006-02-21 19:23 ` Matt Mackall
2006-02-21 19:58 ` David S. Miller
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=20060221.121948.60060362.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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