From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: circular console list in 2.6.9-bk3+
Date: Fri, 19 Nov 2004 00:59:47 +0000 [thread overview]
Message-ID: <20041119005947.GM2268@holomorphy.com> (raw)
In-Reply-To: <20041118144142.GG2268@holomorphy.com>
On Thu, 18 Nov 2004 06:41:42 -0800 William Lee Irwin III <wli@holomorphy.com> wrote:
>> Some changes that added serial console retry logic aren't interacting
>> well with PROM console setup and teardown and whatever sunzilog.c does,
>> and appear to result in a circular console list (hence indefinitely
>> repeated output). The trick is, of course, that I'm not sure which of
>> the three is wrong.
On Thu, Nov 18, 2004 at 02:36:53PM -0800, David S. Miller wrote:
> Please elaborate.
> sunzilog_console_init() will be called at most one time and
> therefore it will register itself one time via register_console().
> I don't see how anything in register_console() can wind us up with
> a circular list, and thus the problem you seem to be describing.
We were doing okay until the following patch got merged. Then (booting
with -p and console=ttyS0,9600) it loops printk'ing the string
"PROMLIB: Sun IEEE Boot Prom 3.2.30 2002/10/25 14:03"
indefinitely.
-- wli
ChangeSet 1.1988.93.9, 2004/10/19 16:11:22+01:00, rmk@flint.arm.linux.org.uk
[SERIAL] Keep trying to register our console device.
Some serial drivers receive their serial port device information via
the device model. This unfortunately means that the selected port
may not be available when the console subsystem initialises, so we
must keep trying to register the console after each port is added.
serial_core.c | 9 +++++++++
1 files changed, 9 insertions(+)
diff -Nru a/drivers/serial/serial_core.c b/drivers/serial/serial_core.c
--- a/drivers/serial/serial_core.c 2004-10-19 20:33:48 -07:00
+++ b/drivers/serial/serial_core.c 2004-10-19 20:33:48 -07:00
@@ -2225,6 +2225,15 @@
*/
tty_register_device(drv->tty_driver, port->line, port->dev);
+ /*
+ * If this driver supports console, and it hasn't been
+ * successfully registered yet, try to re-register it.
+ * It may be that the port was not available.
+ */
+ if (port->type != PORT_UNKNOWN &&
+ port->cons && !(port->cons->flags & CON_ENABLED))
+ register_console(port->cons);
+
out:
up(&port_sem);
next prev parent reply other threads:[~2004-11-19 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 14:41 circular console list in 2.6.9-bk3+ William Lee Irwin III
2004-11-18 22:36 ` David S. Miller
2004-11-19 0:59 ` William Lee Irwin III [this message]
2004-11-19 1:06 ` William Lee Irwin III
2004-11-19 3:00 ` David S. Miller
2004-11-20 10:04 ` William Lee Irwin III
2004-11-20 20:06 ` 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=20041119005947.GM2268@holomorphy.com \
--to=wli@holomorphy.com \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.