From: Reinhard Nissl <rnissl@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: SysReq & serial console
Date: Mon, 02 Jan 2006 21:16:25 +0100 [thread overview]
Message-ID: <43B98A19.8070002@gmx.de> (raw)
In-Reply-To: <20060102091808.GA11673@flint.arm.linux.org.uk>
Hi,
Russell King 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.
On my SuSE 10 system, I find the following lines in /etc/syslog.conf:
# print most on tty10 and on the xconsole pipe
#
kern.warning;*.err;authpriv.none /dev/tty10
kern.warning;*.err;authpriv.none |/dev/xconsole
Changing tty10 to ttyS0 and restarting rcsyslog has no influence on the
output of SysReq commands, but obviously they now nolonger appear on
tty10. So what's the correct way to delegate the output to serial console?
PS: kernel command line: ... console=ttyS0,115200 console=tty0
BTW: a short update of my freeze issue:
- memtest86 revealed a bad memory location
- accidentially beeing at tty10 when the freeze happend and sysrq-p
showed that the atheros module got stuck
- exchanging RAM and disabling ath0 seems to cure the system for 39
minutes so far ;-)
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:rnissl@gmx.de
next prev parent reply other threads:[~2006-01-02 20:16 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
2006-01-02 9:18 ` Russell King
2006-01-02 20:16 ` Reinhard Nissl [this message]
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=43B98A19.8070002@gmx.de \
--to=rnissl@gmx.de \
--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