Rik van Riel (riel@conectiva.com.br) writes:
> On Mon, 10 Apr 2000, Ed Carp wrote:
>
> > 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.
The box in question, unfortunately, is running 2.0.30 - the magic sysrq stuff
is unavailable.
> 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??
That would be cool :) I'm not really up to speed on the keyboard interface via
the serial port - anyone want to throw me a clue as to where to look to change
code?
-
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 : Sat Apr 15 2000 - 21:00:14 EST