mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: mpm@selenic.com
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: softlockup interaction with slow consoles
Date: Tue, 21 Feb 2006 11:58:59 -0800 (PST)	[thread overview]
Message-ID: <20060221.115859.92015829.davem@davemloft.net> (raw)
In-Reply-To: <20060221192340.GO4650@waste.org>

From: Matt Mackall <mpm@selenic.com>
Date: Tue, 21 Feb 2006 13:23:40 -0600

> I don't like it. We should instead just have printk tickle the watchdog.

You can't, interrupts are disabled the entire time and thus
jiffies aren't advancing.  The "touch" just sets the local
cpu timestamp to whatever jiffies is.

That's the problem.

I agree that it would be nice to fix this, but the desire for
synchronous console output makes this very hard to solve.

Like I said, maybe some local chunking in release_console_sem()
but since interrupts will come in we can trigger more and more
lengthy console output and eventually overflow the printk log
buffer before the chunking loop can catch up and we'll thus
lose messages.

      reply	other threads:[~2006-02-21 20:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 21:18 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
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 [this message]

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.115859.92015829.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mpm@selenic.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

Powered by JetHome