Serious reproducible 2.4.x kernel hang

From: Chris Evans (
Date: Thu Feb 01 2001 - 09:14:09 EST


I've just managed to reproduce this personally on 2.4.0. I've had a report
that 2.4.1 is also affected. Both myself and the other person who
reproduced this have SMP i686 machines, which may or may not be relevant.

To reproduce, all you need to do is get my vsftpd ftp server:

It runs from inetd. Connect using the Linux command line ftp client, to
localhost, and simply press CTRL-C. If it matters, I'm using RH7.0

After the first iteration of this, I'm left with:
[chris@localhost chris]$ ps auwx | grep ftp
root 713 99.9 0.4 1416 592 ? SN 22:01 38:17 vsftpd
nobody 715 0.0 0.0 0 0 ? ZN 22:01 0:00 [vsftpd

As you can see, the root process is burning 100% of one of my CPUs. It
_cannot_ be killed with kill -9!

>From Alt-Sysrq-T:
Jan 30 22:01:52 localhost kernel: vsftpd S 00000000 860 713 670
Jan 30 22:01:52 localhost kernel: Call Trace:
[smp_apic_timer_interrupt+240/272] [smp_apic_timer_interrupt+240/272]
[update_process_times+32/160] [smp_apic_timer_interrupt+240/272]
[remove_wait_queue+6/48] [wait_for_packet+273/288]
Jan 30 22:01:52 localhost kernel: [unix_dgram_recvmsg+69/256]
[sock_recvmsg+53/176] [sock_read+134/144] [sys_read+150/208]
Jan 30 22:01:52 localhost kernel: vsftpd Z C5E07040 1408 715 713
Jan 30 22:01:52 localhost kernel: Call Trace: [do_exit+628/672]

As we can see, the 100% CPU broken process has got stuck in a blocking
read() on a unix socket.

If I repeat the ftp connect/CTRL-C process again, I get a totally dead

Hope this is sufficient info. I'll try and write a minimal test case.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

This archive was generated by hypermail 2b29 : Wed Feb 07 2001 - 21:00:12 EST