reproducible 'socked destroy delayed'

Thomas =?ISO-8859-1?Q?K=F6nig?= (Thomas.Koenig@ciw.uni-karlsruhe.de)
Thu, 11 Apr 1996 11:43:11 +0200 (MET DST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Philip Blundell: "Re: Parallel, IEEE 1284, Zip drive"
Previous message: Ingo Molnar: "Re: 1.3.86: double lock on device queue! + Socket destroy delayed"

I can still cause two 'socked destroy delayed' errors by pinging a
nonexistent host on a local network in 1.3.86, then interrupting
the ping process. The error has remained unchanged for quite a
long time, and I've reported full details several times. If
anybody's interested, I can send them.

Is it time to set up an automailer, which checks for this bug and
sends a bug report every time I boot up a new kernel version? :-)

-- 
Thomas Koenig, Thomas.Koenig@ciw.uni-karlsruhe.de, ig25@dkauni2.bitnet.
The joy of engineering is to find a straight line on a double
logarithmic diagram.

Next message: Philip Blundell: "Re: Parallel, IEEE 1284, Zip drive"
Previous message: Ingo Molnar: "Re: 1.3.86: double lock on device queue! + Socket destroy delayed"