Hi
With yesterday's current I get repeating panics while having increased
tcp traffic. I don't know if this is really tcp related.
A backtrace is attached. I'll supply more info if needed.
bye
--
Tobias Reifenberger -- [EMAIL PROTECTED] -- DG1NGT
GEE e* dpu s:- a-- C+++ UB+++ L- W+ N+ w--- Y+ t
> > If persist timer is working, and if it happen to timeout between
> > callout_reset(tp->tt_rexmt, tp->t_rxtcur,
> > tcp_timer_rexmt, tp);
> > and
> > callout_stop(tp->tt_persist);
> > then the panic might happen a
< said:
> If persist timer is working, and if it happen to timeout between
> callout_reset(tp->tt_rexmt, tp->t_rxtcur,
> tcp_timer_rexmt, tp);
> and
> callout_stop(tp->tt_persist);
> then the panic might happe
It looks fine to me.
Perhaps Garrett has something to say about it?
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
<[EMAIL PROTECTED]> bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 2
-On [2221 12:01], Luigi Rizzo ([EMAIL PROTECTED]) wrote:
>> this is fun...
>>
>> Just caught panic #3 on my Diablo newstransit box running 4.0 from the
>> 7th of February.
>>
>> This box pushes around 360-380 GB in a weekend on network IO.
>
>this is the right kind of app for -current isn't
> >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) prin
-On [2221 14:40], Yoshinobu Inoue ([EMAIL PROTECTED]) 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_p
> >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
-On [2221 12:15], Sameh Ghane ([EMAIL PROTECTED]) wrote:
>Le Mon, Feb 21, 2000 at 11:07:52AM +0100, Jeroen Ruigrok van der Werven écrivit:
>> Just caught panic #3 on my Diablo newstransit box running 4.0 from the
>> 7th of February.
My first two were ffs related. And I hadn't enabled DDB and
-On [2221 13:30], Yoshinobu Inoue ([EMAIL PROTECTED]) wrote:
>> >Might there be incorrect memory over writing?
>>
>> How you mean?
>
>I think one possibility of the problem is that some code is
>incorrectly overwriting some part of the memory, and a tcpcb's
>tt_persist->c_flags is happen to o
> >Might there be incorrect memory over writing?
>
> How you mean?
I think one possibility of the problem is that some code is
incorrectly overwriting some part of the memory, and a tcpcb's
tt_persist->c_flags is happen to overwritten.
Now I am very much interested in the value of
tp->tt_persis
-On [2221 12:45], Yoshinobu Inoue ([EMAIL PROTECTED]) wrote:
>> > Just caught panic #3 on my Diablo newstransit box running 4.0 from the
>> > 7th of February.
>
>> We have 60GB IN/OUT each day, and it runs fine:
>>
>> $ uptime
>> 12:09PM up 46 days, 17:19, 1 user, load averages: 0.62, 0.66,
> > Just caught panic #3 on my Diablo newstransit box running 4.0 from the
> > 7th of February.
> We have 60GB IN/OUT each day, and it runs fine:
>
> $ uptime
> 12:09PM up 46 days, 17:19, 1 user, load averages: 0.62, 0.66, 0.64
>
> 4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed Jan 5 14:36:46 CET 20
Le Mon, Feb 21, 2000 at 11:07:52AM +0100, Jeroen Ruigrok van der Werven écrivit:
> Well,
>
> this is fun...
>
> Just caught panic #3 on my Diablo newstransit box running 4.0 from the
> 7th of February.
>
> This box pushes around 360-380 GB in a weekend on network IO.
>
> panic: tcp_setpersist:
> this is fun...
>
> Just caught panic #3 on my Diablo newstransit box running 4.0 from the
> 7th of February.
>
> This box pushes around 360-380 GB in a weekend on network IO.
this is the right kind of app for -current isn't it :)
cheers
luigi
To Unsubscribe: send mail to [
Well,
this is fun...
Just caught panic #3 on my Diablo newstransit box running 4.0 from the
7th of February.
This box pushes around 360-380 GB in a weekend on network IO.
panic: tcp_setpersist: retransmit pending
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.354
db>
16 matches
Mail list logo
