From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Console output for debugging
Date: 22 Jan 2002 15:34:45 -0800 [thread overview]
Message-ID: <a2ksul$6v5$1@cesium.transmeta.com> (raw)
In-Reply-To: <3C4DF2AD.66BC3F6C@cicese.mx>
Followup to: <3C4DF2AD.66BC3F6C@cicese.mx>
By author: Serguei Miridonov <mirsev@cicese.mx>
In newsgroup: linux.dev.kernel
>
> Q: Is there any function in the kernel which I can call
> safely from a module to print debug message on the console
> screen?
>
> I don't want to use printk for some reasons. One of them is
> that I want messages to appear on the screen immediately,
> even from interrupt processing routines. Another is to be
> able to see messages until the system freezes completely in
> case of software or hardware bug.
>
Use printk.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-01-22 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 23:15 Console output for debugging Serguei Miridonov
2002-01-22 23:31 ` Dave Jones
2002-01-22 23:34 ` H. Peter Anvin [this message]
2002-01-23 18:09 ` root
2002-01-22 23:42 ` Andrew Morton
2002-01-23 18:02 ` Serguei Miridonov
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='a2ksul$6v5$1@cesium.transmeta.com' \
--to=hpa@zytor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox