tech-net archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: panic: sbdrop

In article <>,
Manuel Bouyer  <> wrote:
>Hi again,
>on this netbsd-5 box (test NFS server with 2 fast linux clients) I got
>(after fixing m_split() to handle 0 len, see previous mail):
>panic: sbdrop
>fatal breakpoint trap in supervisor mode
>trap type 1 code 0 eip c03faa4c cs 8 eflags 246 cr2 cdb59000 ilevel 4
>Stopped in pid 0.3 (system) at  netbsd:breakpoint+0x4:  popl    %ebp
>db{0}> tr
> at netbsd:breakpoint+0x4
> at netbsd:panic+0x1b0
>sbdrop(c3ba07e0,e8,c3c1446c,14,20,0,c3b40d00,14,cd13bca8,ce320030) at
>tcp_input(c3c14400,14,6,1,c01280ea,cbf87a00,0,0,14,cbf87a00) at
>at netbsd:ip_input+0x61f
>at netbsd:ipintr+0x4d
>softint_dispatch(cbf87c80,4,0,0,0,0,cd13bd90,cd13ba68,cd13bac0,18) at
>DDB lost frame for netbsd:Xsoftintr+0x3d, trying 0xcd13bd88
>Xsoftintr() at netbsd:Xsoftintr+0x3d
>I have a core dump and netbsd.gdb
>Any idea ?

change tcp_input.c:1749
    sbdrop(&so->so_snd, acked);
    sbdrop(&so->so_snd, MIN(acked, (int)so->so_snd.sb_cc));

It seems that it is checking that in the other place it calls sbdrop
in tcp_input.c, or perhaps I don't know what I am talking about!


Home | Main Index | Thread Index | Old Index