Double lock on socket - 1.3.69

Double lock on socket - 1.3.69

Post by Andrew Ro » Thu, 29 Feb 1996 04:00:00

I'm still getting the occasional

Feb 28 14:07:09 gandalf kernel: double lock on socket at 00143533

with kernel 1.3.69. It doesn't seem to actually cause any problems. The
relevant section of is

00142a30 t do_tcp_sendmsg
001434a0 t tcp_sendmsg
001435c0 T tcp_read_wakeup
00143880 t tcp_recv_urg
00143a50 t cleanup_rbuf

There was no particularly heavy network load at the time - just a couple
of rlogins to other machines and localhost tcp conections for my x font
server. Anyone else getting these messages?


   Churchill College    Tel (01223) 331594
   Cambridge CB3 0DS    


1. Is 1.3.69 most recent most stable?

I downloaded what I read was supposed to be the latest kernel,
compiler, utilities, etc... for building the new kernel.  It
seems to have blown up and, being a linux newbie, I'm not sure
why.  (Having two 300Mb+ linux partitions prevented self
inflicted disaster.)  Is 1.3.69 more stable than 1.3.100?  What
order do I rebuild a 'new' system.  I don't mind the pains of
learning one's lessons.  I *would* like more info on what
modules, gcc, etc... go together.  Do I recompile gcc.latest.
then  Then modules, utilities, then
everything else I can't live without?...   I would appreciate any
information (even constructive sarcasm would be better that
stabbing in the dark).  Thanks....   Dale

2. 2.4.1ac13/14 problem

3. qic-02 Archive SC402 and 1.3.69

4. screen scrolling with tcsh

5. xconfig in 1.3.69

6. Masquerading + CUSEEME help

7. xemacs 19-13 & linux 1.3.69 (ELF)

8. Evanescent Screen Messages??

9. 1.3.69 and ftape

10. 1.3.69 Can't add NCPfs support...

11. Two quick question about configuring the 1.3.69 kernel.

12. Strange console boot-time message with 1.3.69 kernel.

13. HOLY SHIT! Looks like a serious problem in kernel 1.3.69.