public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andy Whitcroft <apw@canonical.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Crutcher Dunnavant <crutcher+kernel@datastacks.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] sysrq documentation: document why the command header only is shown
Date: Wed, 07 Jan 2009 15:30:29 -0800	[thread overview]
Message-ID: <49653B15.4090901@oracle.com> (raw)
In-Reply-To: <1231364958-26253-3-git-send-email-apw@canonical.com>

Andy Whitcroft wrote:
> Document the interactions between loglevel and the sysrq output.  Also
> document how to work round it should output on the console be required.
> 
> Signed-off-by: Andy Whitcroft <apw@canonical.com>
> ---
>  Documentation/sysrq.txt |   18 ++++++++++++++++++
>  1 files changed, 18 insertions(+), 0 deletions(-)
> 
> diff --git a/Documentation/sysrq.txt b/Documentation/sysrq.txt
> index 265f637..a262ffb 100644
> --- a/Documentation/sysrq.txt
> +++ b/Documentation/sysrq.txt
> @@ -210,6 +210,24 @@ within a function called by handle_sysrq, you must be aware that you are in
>  a lock (you are also in an interrupt handler, which means don't sleep!), so
>  you must call __handle_sysrq_nolock instead.
>  
> +*  When I hit a sysrq combination only the header appears on the console, why?

   *  When I hit a sysrq key combination, only the header appears on the console. Why?
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +Sysrq output is subject to the same console loglevel control as all
> +other console output.  This means that if the kernel was booted 'quiet'
> +as is common on distro kernels the output may not appear on the actual
> +console, even though it will appear in the dmesg buffer, and be accessible
> +via the dmesg command and to the consumers of /proc/kmsg.  As a specific
> +exception the header line from the sysrq command is passed to all console
> +consumers as if the current loglevel was maximum.  If only the header
> +is emitted it is almost cirtain that the kernel loglevel is too low.

                           certain

> +Should you require the output on the console channel then you will need
> +to temporarily up the console loglevel using alt-sysrq-8 or:
> +
> +    echo 8 > /proc/sysrq-trigger
> +
> +Remember to return the loglevel to normal after triggering the sysrq
> +command you are interested in.
> +
>  *  I have more questions, who can I ask?
>  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  And I'll answer any questions about the registration system you got, also


-- 
~Randy

  reply	other threads:[~2009-01-07 23:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 12:37 sysrq loglevel Andy Whitcroft
2009-01-07 19:25 ` Andrew Morton
2009-01-07 20:50   ` Andy Whitcroft
2009-01-07 21:49     ` [PATCH 0/3] document sysrq interaction with loglevels Andy Whitcroft
2009-01-07 21:49       ` [PATCH 1/3] sysrq documentation: remove the redundant updated date Andy Whitcroft
2009-01-07 21:49       ` [PATCH 2/3] sysrq documentation: document why the command header only is shown Andy Whitcroft
2009-01-07 23:30         ` Randy Dunlap [this message]
2009-01-07 21:49       ` [PATCH 3/3] sysrq: add commentary on why we use the console loglevel over using KERN_EMERG Andy Whitcroft
2009-01-08  8:44         ` Nick Andrew
2009-01-08  2:10     ` [PATCH 0/3] document sysrq interaction with loglevels V2 Andy Whitcroft
2009-01-08  2:10       ` [PATCH 1/3] sysrq documentation: remove the redundant updated date Andy Whitcroft
2009-01-08  2:10       ` [PATCH 2/3] sysrq documentation: document why the command header only is shown Andy Whitcroft
2009-01-08  2:10       ` [PATCH 3/3] sysrq: add commentary on why we use the console loglevel over using KERN_EMERG Andy Whitcroft

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=49653B15.4090901@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=crutcher+kernel@datastacks.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