Re: panic: tcp_do_segment: sent too much

2025-03-19 Thread Michael Tuexen
gt;>> running at 2832af7b4ea256b18ef4dbf2ff97a50765f0609a: >>> >>> panic: tcp_do_segment: sent too much >>> cpuid = 5 >>> time = 1736731772 >>> KDB: stack backtrace: >>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >>&g

Re: panic: tcp_do_segment: sent too much

2025-03-19 Thread Kyle Evans
On 1/13/25 13:01, Michael Tuexen wrote: On 13. Jan 2025, at 02:44, Kyle Evans wrote: Hi, I seem to have hit this panic during normal laptop usage with a -CURRENT running at 2832af7b4ea256b18ef4dbf2ff97a50765f0609a: panic: tcp_do_segment: sent too much cpuid = 5 time = 1736731772 KDB: stack

Re: panic: tcp_do_segment: sent too much

2025-01-13 Thread Michael Tuexen
> On 13. Jan 2025, at 02:50, Zhenlei Huang wrote: > > > >> On Jan 13, 2025, at 9:44 AM, Kyle Evans wrote: >> >> Hi, >> >> I seem to have hit this panic during normal laptop usage with a -CURRENT >> running at 2832af7b4ea256b18ef4dbf2ff97a507

Re: panic: tcp_do_segment: sent too much

2025-01-13 Thread Michael Tuexen
> On 13. Jan 2025, at 02:44, Kyle Evans wrote: > > Hi, > > I seem to have hit this panic during normal laptop usage with a -CURRENT > running at 2832af7b4ea256b18ef4dbf2ff97a50765f0609a: > > panic: tcp_do_segment: sent too much > cpuid = 5 > time = 173

Re: panic: tcp_do_segment: sent too much

2025-01-12 Thread Ronald Klop
Seen this before. Does one of these issues match your case? https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=Tcp_do_segment&list_id=789107 Regards, Ronald Van: Kyle Evans Datum: 13 januari 2025 02:45 Aan: freebsd-net@freebsd.org Onderwerp: panic: tcp_do_segment: sent too

panic: tcp_do_segment: sent too much

2025-01-12 Thread Kyle Evans
Hi, I seem to have hit this panic during normal laptop usage with a -CURRENT running at 2832af7b4ea256b18ef4dbf2ff97a50765f0609a: panic: tcp_do_segment: sent too much cpuid = 5 time = 1736731772 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame

Re: panic: tcp_do_segment: sent too much

2025-01-12 Thread Zhenlei Huang
> On Jan 13, 2025, at 9:44 AM, Kyle Evans wrote: > > Hi, > > I seem to have hit this panic during normal laptop usage with a -CURRENT > running at 2832af7b4ea256b18ef4dbf2ff97a50765f0609a: > > panic: tcp_do_segment: sent too much > cpuid = 5 > time = 173

Re: panic: tcp_do_segment: sent too much

2024-10-23 Thread Michael Tuexen
t;> + export 'TESTPROGS= ./testcases/tcp/tcp' >>> + sleep 900 >>> + su test -c '(cd ..; ./testcases/run/run $TESTPROGS)' >>>run: run time 0+00:15:00, incarnations 1, load 100, verbose 1 >>> 23:59:21 Loop #1 >>>tcp: run time 0+

Re: panic: tcp_do_segment: sent too much

2024-10-23 Thread Peter Holm
> > + su test -c '(cd ..; ./testcases/run/run $TESTPROGS)' > > run: run time 0+00:15:00, incarnations 1, load 100, verbose 1 > > 23:59:21 Loop #1 > > tcp: run time 0+00:02:00, incarnations 3202, load 100, verbose 1 > > witness_lock_list_get: witnes

Re: panic: tcp_do_segment: sent too much

2024-10-22 Thread Michael Tuexen
0+00:15:00, incarnations 1, load 100, verbose 1 > 23:59:21 Loop #1 > tcp: run time 0+00:02:00, incarnations 3202, load 100, verbose 1 > witness_lock_list_get: witness exhausted > panic: tcp_do_segment: sent too much > cpuid = 6 > time = 1729634436 > KDB: sta

panic: tcp_do_segment: sent too much

2024-10-22 Thread Peter Holm
0+00:02:00, incarnations 3202, load 100, verbose 1 witness_lock_list_get: witness exhausted panic: tcp_do_segment: sent too much cpuid = 6 time = 1729634436 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe01081bd9b0 vpanic() at vpanic+0x13f/frame 0xfe01