Date: Mon, 21 Feb 2000 14:48:59 +0100 From: Jeroen Ruigrok van der Werven <asmodai@bart.nl> To: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp> Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) Message-ID: <20000221144858.O84100@lucifer.bart.nl> In-Reply-To: <20000221223459W.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Mon, Feb 21, 2000 at 10:34:59PM %2B0900 References: <20000221125010.H84100@lucifer.bart.nl> <20000221212656L.shin@nd.net.fujitsu.co.jp> <20000221134724.J84100@lucifer.bart.nl> <20000221223459W.shin@nd.net.fujitsu.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
-On [20000221 14:40], Yoshinobu Inoue (shin@nd.net.fujitsu.co.jp) wrote:
>> >Now I am very much interested in the value of
>> >tp->tt_persist->c_flags at panic, if CALLOUT_PENDING and
>> >possibly other flags are just set, or completely broken data
>> >is written on it.
>>
>> 893
>> (kgdb) print tp->tt_persist->c_flags
>> $1 = 0
>
>Woops sorry I was worng.
>tp->tt_rexmt->c_flags is actually causing the panic, and the
>necessary data is the contents of the tp->tt_rexmt->c_flags.
(kgdb) print tp->tt_rexmt->c_flags
$1 = 6
(kgdb) print tp->tt_rexmt
$2 = (struct callout *) 0xd5ce6c2c
(kgdb) print (*tp->tt_rexmt)
$3 = {c_links = {sle = {sle_next = 0xd5cd7c2c}, tqe = {tqe_next = 0xd5cd7c2c,
tqe_prev = 0xd5cd83ac}}, c_time = 22275144, c_arg = 0xd5ce6b60,
c_func = 0xc018bcdc <tcp_timer_rexmt>, c_flags = 6}
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
<asmodai@bart.nl> bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000221144858.O84100>