Hi Rik.
>> We're doing a port of both 2.0.30 and 2.2.14 to a, um,
>> less-than-compliant PPC. We're seeing Linux go out to
>> lunch after about 3 weeks or so of operation. I talk to
>> a terminal server that talks to the Linux box through
>> the serial port, so the usual way of doing things with
>> shift/scroll-lock won't work. Anyone have an idea as to
>> how I can debug this box? TIA :)
> A good solution might be to have the various sysrq things
> available from files in /proc/, drivers/char/sysrq.c is
> the file you want to look at.
> Of course this no longer helps you after things have
> crashed, so maybe we want an alternate key combination
> to get at the sysrq info over serial console??
How about making use of the so-called "break key" that can be
sent over the serial link by just about any terminal emulator?
When one is using a serial combination, the first character
after receipt of such is taken as being a SysRq code and acted
on as if pressed with SysRq.
Best wishes from Riley.
* Copyright (C) 2000, Memory Alpha Systems.
* All rights and wrongs reserved.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* http://www.memalpha.cx/Linux/Kernel/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 30 2000 - 21:00:09 EST