Date: Fri, 19 Nov 2004 14:34:28 +0100 (CET) From: =?iso-8859-2?Q?S=B3awek_=AFak?= <zaks@prioris.mini.pw.edu.pl> To: "Robert Watson" <rwatson@freebsd.org> Cc: pjd@freebsd.org Subject: Re: Network related panic on FreeBSD 5.3-STABLE/AMD64 Message-ID: <20041119133428.59D3C11445@localhost> References: <Pine.NEB.3.96L.1041119130741.92822E-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Robert Watson" <rwatson@freebsd.org> writes:
> On Fri, 19 Nov 2004, [iso-8859-2] Sławek Żak wrote:
>
>> "Robert Watson" <rwatson@freebsd.org> writes:
>>
>> > On Fri, 19 Nov 2004, Robert Watson wrote:
>> >
>> >>
>> >> On Fri, 19 Nov 2004, Slawek Zak wrote:
>> >>
>> >> > I can reproduce it easily,
>> >> >
>> >> > The panic message and backtrace is:
>> >>
>> >> Could I get you to convert the symbol+offsets below to line numbers
>> >> using gdb on a copy of your kernel with debugging symbols? In
>> >> particular, the offsets into tcp_output, tcp_input, and ip_input.
>>
>> Here are the offsets:
>>
>> tcp_input.c:1993
>> tcp_output.c:804
>> ip_input.c:743
>>
>> As for SOCKBUF_DEBUG I'll reboot and try.
>
> Using the core, could you also print the contents of *so and
> *so->so_snd.sb_mb in the tcp_output frame?
The problem is, that I cannot obtain proper backtrace in gdb, so I cannot
get to the tcp_output frame. I've found the above locations with addr2line
and a pocket calculator. Take a look at the gdb session:
# kgdb kernel.debug vmcore.0
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd".
0x00000000 in ?? ()
(kgdb)
(kgdb) bt
#0 0x00000000 in ?? ()
pjd@ told me to try and disable SACK. The machine worked fine without SACK
enabled for 30 minutes then 2 minutes after I've re-enabled SACK it crashed
again with the same panic message.
All patches are most welcome.
Thanks, /S
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041119133428.59D3C11445>