From: Dan Kegel <dank@kegel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: printk in init_module mixing with printf in insmod
Date: Fri, 19 Apr 2002 11:39:44 -0700 [thread overview]
Message-ID: <3CC06470.F05543C4@kegel.com> (raw)
I recently upgraded my ppc405 embedded system
from 2.4.2 or so to 2.4.17 or so. I use modutils-2.4.12.
When I insert a nongpl module,
the
fprintf(stderr, "Warning: loading foo.o will taint kernel\n");
in insmod and the
printk("Hello, world\n");
in the module are intermixed unpleasantly, yielding output like
Warning: loHello,ading foo.o world
will taint kernel
This garbled output makes reading the debugging printk's difficult.
I suppose this isn't terribly important, since printk's are
kind of a no-no in production, and this only affects printk's
in init_module, but it'd be nice to know what
the cleanest way to get rid of the mixing is. Adding a sleep
inside insmod seems heavyhanded. I suppose I could redirect
insmod's output to a file, sleep a bit, and then display the
file... bleah.
- Dan
next reply other threads:[~2002-04-19 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 18:39 Dan Kegel [this message]
2002-04-19 18:47 ` printk in init_module mixing with printf in insmod Russell King
2002-04-19 19:51 ` Dan Kegel
2002-04-19 22:24 ` Alan Cox
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=3CC06470.F05543C4@kegel.com \
--to=dank@kegel.com \
--cc=linux-kernel@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.