Two 2.2.2 problems (was Re: 2.2.2 processes stuck in 'D' state doing mean things to FS

Drago Goricanec (drago@king.otsd.ts.fujitsu.co.jp)
Thu, 25 Feb 1999 13:44:32 +0900


On Tue, 23 Feb 1999 00:22:50 -0500 (EST),
David Mansfield <david@cobite.com> writes:

david> I was doing a 'load test' on the new kernel and managed to get three
david> processes stuck in 'D'. Here's output from ps -alx (applicable procs.):
david>
david> FLAGS UID PID PPID PRI NI SIZE RSS WCHAN STA TTY TIME COMMAND
david> 800 0 1285 1284 0 0 876 0 wait_on_sup DW p1 0:00 (tar)
david> 0 0 1316 1288 0 0 772 0 wait_on_sup DW p2 0:00 (rm)
david> 0 0 1319 1302 0 0 760 0 down_failed DW p3 0:00 (rm)
david>
david> Kernel is SMP 2.2.2 + DAC960 Raid Beta4 compiled w/gcc2.7.2.3, RedHat 5.2.
david> 256MB. There is only 1 cpu (450 MHZ Intel PII) installed (other goes in
david> tomorrow, maybe :-( but it is compiled SMP.

I seem to have experienced a similar problem, but I didn't have to
stress the system at all.

I upgraded to 2.2.2 from 2.0.36 because I needed 2048 bytes/sector
support for my new Fujitsu 1.3 GB MO drive.

The system is based on RedHat 5.1 + everything in mentioned in
Documentation/Changes except for procps (still at 1.2.7) and chsh). I
will upgrade these tonight.

I've got a 300 MHz Intel PII, 256 MB RAM, UP (not SMP), and the
Adaptec 294x UW SCSI controller.

Problem 1:

When I tried to mke2fs on a 1.3GB MO drive, it wrote out only about 16
out of 760+ inode tables when the process seemed to get stuck. The
first time it seemed to stick at 3, then jumped to 5. I was able to
kill the task, but it took 10-15 seconds before it actually
terminated. When I retried, it got a little further, but never beyond
about 16 inode tables.

Problem 2:

I dialed up my ISP, and tried to telnet to a couple of different
hosts, but after the initial connection was made, no data seemed to be
exchanged (per tcpdump).

Sorry for the lack of hard data to support these problem reports. I
will try to collect it, but in the mean time, I wan't to see if other
people have been experiencing similar problems with 2.2.2.

regards,
Drago

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