To: linux-kernel@vger.kernel.org
From: Kalin KOZHUHAROV <kalin@thinrope.net>
Subject: Re: SysReq & serial console
Date: Wed, 11 Jan 2006 14:51:12 +0900
Message-ID: <dq26cg$3el$1@sea.gmane.org>
References: <43B8696B.2070303@gmx.de> <dpakp2$tip$3@sea.gmane.org> <20060102091808.GA11673@flint.arm.linux.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060110)
In-Reply-To: <20060102091808.GA11673@flint.arm.linux.org.uk>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1183
Lines: 28

Russell King wrote:
> On Mon, Jan 02, 2006 at 04:29:38PM +0900, Kalin KOZHUHAROV wrote:
> 
>>Another wild guess: the syslog is still running and writes the output to
>>the log.
> 
> 
> I don't think syslog can influence whether you see sysrq output via the
> console.  Nevertheless, try sysrq-8 before other sysrq functions.
> 
While playing with a borked 2.6.15 box and syslog-ng, I ran across this again.

The issue is that syslog-ng can use /proc/kmesg as a source for logging and
if this is the case, then (intentionally or not), it sucks all the MSGs and
if not setup correctly MSGs from kernel will go to nowhere. The relevant
syslog-ng setup is:

source foo { pipe("/proc/kmsg"); };

This might be a problem/feature/bug with syslog-ng, but I still find it more
natural to see the output of SysRq and oopses on the console as well.

Kalin.

-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|

-
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/