Re: System lockup when stracing xntpd

Simon Richter (geier@phobos.fachschaften.tu-muenchen.de)
Sat, 1 May 1999 14:10:15 +0200 (CEST)


Whoops, forgot to copy the list.

---------- Forwarded message ----------
Date: Sat, 1 May 1999 13:58:39 +0200 (CEST)
From: Simon Richter <geier@phobos.fachschaften.tu-muenchen.de>
To: Bradley Baetz <bbaetz@ug.cs.usyd.edu.au>
Subject: Re: System lockup when stracing xntpd

On Sat, 1 May 1999, Bradley Baetz wrote:

> The strace stops there. Control-C doesn't stop it, and SysRq-K, SysRq-S,
> and Sysrq-U print their various messages (SysRq: Emergency Sync and so
> on), but without actually doing anything. I could change VTs, but
> couldn't type on them, even on one running a bash shell niced to -20.
> SysRq-E killed all processes except for init, and then the system
> behaved normally.

This sounds much the same as what I'm experiencing with my Amiga here
(kenel 2.0.36 [as from the Debian 2.1 rescue floppy] on an A1200 w/
Apollo 1240 Turboboard, 10gig HD on the internal controller, 2MB chip
mem, 32MB fast local mem, everything else plain vanilla).

When I tar -xzf a file bigger than about 2MB, the system locks up, I can
switch consoles, but I cannot type, Ctrl-Alt-Del doesn't work,
Ctrl-Amiga-Amiga does the usual thing ("C-A-A reset warning. System will
reboot in 10 seconds"). I cannot say whether gzunzipping and untarring in
separate steps will work. I will try that when I come home (been in the
university all night).

> Commenting out the bits in the xntpd source code which set the
> scheduling priority to SCHED_FIFO allowed the strace to continue
> normally. I couldn't find a simple test case program to exhibit the same
> problem, but a program which sets the scheduling to SCHED_FIFO, and then
> calls fork(), hung at fork( when strace -f'd, but I could stop that with
> Contorl-C.

A short grep over the sources shows that tar doesn't know about
SCHED_FIFO. I'm not sure if this is the same problem or caused by the same
thing (Although the kernel is rewritten from scratch, the developers'
ideas aren't). If anyone has a 2.2 tree that compiles for m68k, I could
do some additional testing. If someone is interested, I put a .config
matching my setup on http://phobos.fs.tum.de/stuff/.config

Simon

-
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/