[lkml]   [1997]   [May]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subject2.0.30 crash with GP data!
    My new server that's crashed a few times just did again...but this time I
    got debug output rather than black screen-o-death.

    TCP: **bug**: copy=0, sk->mss=0
    general protection: 0000
    CPU: 0
    EIP: 0010:[tcp_recvmsg+368/1036]
    EFLAGS: 00010213
    eax: f000e987 ebx: 00000000 ecx: 069fa438 edx: f000f84d
    esi: 069fa4d0 edi: 000001b8 ebp: 069fa414 esp: 0542fedc
    ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
    Process irc (pid: 21011, process nr: 102, stackpage=0542f000)
    Stack: 069fa414 0542ff70 00000000 00000000 3d67bc34 069fa438 00000000 000001b8
    0761b414 03c8ba20 2d68b2c9 00150a7e 069fa414 0542ff6c 00000648 00000000
    00000000 0542ff70 001cca68 067c3c40 00000800 03c8ba64 0013782e 03c8ba64
    Call Trace: [inet_recvmsg+114/136] [sys_recv+250/272] [sys_socketcall+525/732] [system_call+85/128]
    Code: 8a 40 0d a8 02 74 04 ff 4c 24 10 8b 7c 24 10 39 7b 30 0f 87
    task already on run-queue
    wait_queue is bad (eip = 0015006b)

    Having just searched the archives, this looks extreemely similar to a
    report posted May 4 by Simon Karpen ( I'll go
    compile a kernel now with Dave's suggested fix posted May 5, but I just
    wonder if anything else was found on this or if there's a more recent fix?

     \ /
      Last update: 2005-03-22 13:39    [W:0.016 / U:4.240 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site