From: "David S. Miller" <davem@davemloft.net>
To: mingo@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: softlockup interaction with slow consoles
Date: Mon, 20 Feb 2006 13:18:47 -0800 (PST) [thread overview]
Message-ID: <20060220.131847.25386315.davem@davemloft.net> (raw)
When register_console() runs, it dumps the entire log buffer
to the console device with interrupts off.
If you're going over a slow console, this can easily take more
than 10 seconds especially on SMP with many cpus brought up.
This makes the softlock fire, which is terribly annoying :-)
I think the bug is in the console registry code, I think it
should capture chunks of the existing console buffer into some
local memory and push things piece by piece with interrupts
enabled to the console driver(s).
Any better ideas?
next reply other threads:[~2006-02-20 21:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 21:18 David S. Miller [this message]
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
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=20060220.131847.25386315.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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®