From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: SysReq & serial console
Date: Mon, 02 Jan 2006 16:29:38 +0900 [thread overview]
Message-ID: <dpakp2$tip$3@sea.gmane.org> (raw)
In-Reply-To: <43B8696B.2070303@gmx.de>
Reinhard Nissl wrote:
> Hi,
>
> I'm facing a similar issue like the thread
>
> system keeps freezing once every 24 hours / random apps crashing
>
> reported, but I still have to try all those suggestions.
>
> For now, I've configured a serial console and enabled SysReq. When the
> freeze happens on my system, the system is still pingable and SysReq can
> for example sync the disks. I also can see on serial console which
> SysReq command I selected (registers, tasks, SAK, etc.), but I do not
> get any output of these commands on serial console.
>
> When issuing such a SysReq command before the system freezes I can see
> the output of the command on a framebuffer console.
>
> So, is it possible to redirect the output of a SysReq command to a
> serial console?
Another wild guess: the syslog is still running and writes the output to the log.
I had this "problem" with syslog-ng running on 2.6.14.4. The solution was to set syslog-ng to write
to tty1 as well (now moved to tty12 to not scramble other MSGs).
I was seeing just something like "SysRq: memory map" and now I can see the output below that MSG.
Not sure if that was inteded to do so, but I think the output of SysRq+<key> is better send to the
console directly...
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
next prev parent reply other threads:[~2006-01-02 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 23:44 SysReq & serial console Reinhard Nissl
2006-01-02 0:37 ` Russell King
2006-01-02 7:29 ` Kalin KOZHUHAROV [this message]
2006-01-02 9:18 ` Russell King
2006-01-02 20:16 ` Reinhard Nissl
2006-01-11 5:51 ` Kalin KOZHUHAROV
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='dpakp2$tip$3@sea.gmane.org' \
--to=kalin@thinrope.net \
--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