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:[email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
