[Bug 254735] rack and bbr panic

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254735

***@gmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@FreeBSD.org

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254735

Michael Tuexen <***@freebsd.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@freebsd.org
Summary|rack and bbr panic |[tcp] rack and bbr panic

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254735

--- Comment #1 from Michael Tuexen <***@freebsd.org> ---
Are the problem reproducible? If yes, how?

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254735

--- Comment #2 from ***@gmail.com ---
(In reply to Michael Tuexen from comment #1)

IMHO configs provided by links should be enough to reproduce configuration.
Panic happen after some time (1-10 min) after I set
net.inet.tcp.functions_default=rack or bbr.
This is home router/firewall/webserver/samba/rtorrent/ssh server.

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254735

--- Comment #3 from Michael Tuexen <***@freebsd.org> ---
(In reply to rozhuk.im from comment #2)
I agree about the config. Was asking about some specific things to do to
reproduce it (like ssh into the box) or something else.

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254735

--- Comment #4 from ***@gmail.com ---
(In reply to Michael Tuexen from comment #3)

Nothing specific that I could describe.
Probably some strange tcp traffic from internet by www/torrent/ssh.
One rule in PF with "flags S/SA synproxy state", few with "flags S/SA modulate
state".

Probably only sysctl.conf would be enough.

This is old bug for me, from 12, I do not report because first reply was "try
with current", and with current in vbox it does not panic.

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254735

--- Comment #5 from Michael Tuexen <***@freebsd.org> ---
(In reply to rozhuk.im from comment #4)
So to be clear:
(a) This bug happens on stable/13 of some days ago
(b) This bug does not happen on current
Are both statements correct?

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254735

Mark Linimon <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Assignee|***@FreeBSD.org |***@FreeBSD.org

[b***@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254735

--- Comment #6 from ***@gmail.com ---
(In reply to Michael Tuexen from comment #5)

a) yes
b) I do not know now. I do tests on current more than year ago.