[lkml]   [1999]   [Jun]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Socket stuck in LAST_ACK for days (2.2.10)
    On Tue, Jun 29, 1999 at 12:50:15PM -0700, wrote:
    > On Tue, 29 Jun 1999, Brian Ristuccia wrote:
    > > tcp 1 38681 LAST_ACK
    > > - off (0.00/0/0)
    > >
    > > This socket stays stuck in LAST_ACK. It's been that way for like 2 days now.
    > > It's blocking that port. Is there any way I can make it go away so I can
    > > restart that daemon without rebooting?
    > I've seen this too on several occasions since the 2.1.x days (At least
    > since the 2.1.9x time frame). I have been unable to reproduce it reliably,
    > or frequently, so I haven't done anything about it yet. I am fair
    > confident that this is due to severe packet loss.


    > I can promise you that this never went away on my systems. It stayed there
    > until the next reboot.

    Hmm... Perhaps I could invite someone to muck around with GDB on my running
    kernel :)

    Hope this gets fixed.

    Brian Ristuccia

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

     \ /
      Last update: 2005-03-22 13:52    [W:0.020 / U:32.080 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site