Message-ID: <49653B15.4090901@oracle.com>
Date: Wed, 07 Jan 2009 15:30:29 -0800
From: Randy Dunlap <randy.dunlap@oracle.com>
Organization: Oracle Linux Engineering
User-Agent: Thunderbird 2.0.0.6 (X11/20070801)
MIME-Version: 1.0
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
References: <1231364958-26253-1-git-send-email-apw@canonical.com> <1231364958-26253-3-git-send-email-apw@canonical.com>
In-Reply-To: <1231364958-26253-3-git-send-email-apw@canonical.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2331
Lines: 52

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/