On Tue, Aug 03, 1999 at 11:06:18AM +1000, Dan Everton wrote:
> On Tue, Aug 03, 1999 at 10:22:49AM +1000, Dan Everton wrote:
> > On Mon, Aug 02, 1999 at 01:21:03PM -0500, Stephen Pitts wrote:
> > > Kinda offtopic suggestion, but rebuild your kernel with
> > > the "magic SysReq" key option, then Alt-
On Tue, Aug 03, 1999 at 10:22:49AM +1000, Dan Everton wrote:
> On Mon, Aug 02, 1999 at 01:21:03PM -0500, Stephen Pitts wrote:
> > Kinda offtopic suggestion, but rebuild your kernel with
> > the "magic SysReq" key option, then Alt-SysRq-K will
>
> Well, unfortunately, magic sysrq is already compile
On Mon, Aug 02, 1999 at 01:21:03PM -0500, Stephen Pitts wrote:
> Kinda offtopic suggestion, but rebuild your kernel with
> the "magic SysReq" key option, then Alt-SysRq-K will
Well, unfortunately, magic sysrq is already compiled in and did nothing.
Tried everything from Alt-SysRq-K to Alt-SysRq-l.
Kinda offtopic suggestion, but rebuild your kernel with
the "magic SysReq" key option, then Alt-SysRq-K will
kill all prorams on the current VC. Running xscreensaver
in the gdb debugger will let you find out where
it crashed and what might have caused the crash.
Try this:
1. Use "apt-get source xs
Just came back from watching TV to note that my X session had locked up and
was unresponsive. The last thing on screen was the graphics displayed by the
"penetrate" screensaver when it changes levels. Went to a friends machine
connected on the same network to ping mine and try and telnet in to kil
5 matches
Mail list logo