[2309] in linux-net channel archive
Socket destroy delayed.
daemon@ATHENA.MIT.EDU (G.W. Wettstein)
Sat Mar 30 07:14:16 1996
From: greg@wind.rmcc.com (G.W. Wettstein)
Date: Sat, 30 Mar 1996 05:55:57 CST
To: linux-net@vger.rutgers.edu
Cc: torvalds@cs.helsinki.fi, net-patches@lxorguk.ukuu.org.uk
Good day to everone, hopefully this note finds everyone's weekend
going well.
Like most other people who are testing the 1.3.x kernels we are being
plagued with socket destroy delayed messages. We are running the
latest versions of the kernel one of our heavily used development
machines to try and exercise them in a production environment.
The particulars of the machine are:
80386dx-33 (Gateway 2K, Old machine)
8 Mbyte RAM
ESDI hard-drive (won't tolerate IDE driver, use old)
SMC WD80x3 ethernet NIC
I spend most of the day rlogin'ed into this machine doing development
of the X front-end code for Perceptions. In addition one of the
serial ports is almost continually busy running an interrogatory
engine which is talking to one of the corporate mainframes. The
results of the interrogation are being fed back through rxvt which is
running locally with its display pointed back to another workstation.
Other than these two activities the machine does nothing else but
basic housekeeping, timed, syslog, cron etc. We have been plagued by
the socket destroy messages since early in the 1.3.7x series. Once an
initial instance occurs they will continue monotonically at a rate of
precisely six per minute.
These messages are always prompted by a 'double lock on device queue'
message. The following is an exercept from the currently running
1.3.79 kernel:
Mar 27 15:53:30 blizard kernel: klogd 1.3-1, log source = ksyslog started.
Mar 27 15:53:32 blizard kernel: Loaded 3305 symbols from /boot/System.map.
Mar 27 15:53:32 blizard kernel: Symbols match kernel version.
Mar 28 15:44:50 blizard kernel: double lock on device queue!
Mar 28 15:44:50 blizard kernel: Socket destroy delayed (r=0 w=252)
Mar 30 04:22:03 blizard last message repeated 6 times
Mar 30 04:23:03 blizard last message repeated 6 times
