[Bug 256657] [tcp] RACK unsuitable for connecting to mysql via network socket on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #15 from Michael Tuexen --- (In reply to Marek Zarychta from comment #14) OK. At the end there is the interaction with the TCP stack. Can you keep the server running using RACK, switch the default stack to FreeBSD, and rerun th

[Bug 256657] [tcp] RACK unsuitable for connecting to mysql via network socket on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #14 from Marek Zarychta --- Created attachment 225883 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=225883&action=edit truss out (In reply to Michael Tuexen from comment #13) >What is the output of >truss mysql -p -

[Bug 256375] iflib/if_em: unplugging network cable causes huge KTorrent slowdown

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256375 --- Comment #14 from Kevin Bowling --- (In reply to Alexey Dokuchaev from comment #11) I think it is probably ok to remove the 'iflib_admin_intr_deferred' line in 'em_if_media_status' but by your numbers it doesn't seem to be causal. There

[Bug 256657] [tcp] RACK unsuitable for connecting to mysql via network socket on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #13 from Michael Tuexen --- (In reply to Marek Zarychta from comment #12) OK. So you set the default stack to RACK, start the database server, start the database client and it stalls. Right. What is the output of truss mysql -

[Bug 256657] [tcp] RACK unsuitable for connecting to mysql via network socket on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #12 from Marek Zarychta --- (In reply to Michael Tuexen from comment #11) >I'm confused. Which config is working and which is not? So am I. I have done another experiment, switched to freebsd stack, restarted database server the

[Bug 256657] [tcp] RACK unsuitable for connecting to mysql via network socket on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #11 from Michael Tuexen --- I'm confused. Which config is working and which is not? Initially you have net.inet.tcp.functions_default=rack and start a server. When you start on the same host the client (which would mean both us

[Bug 256657] [tcp] RACK unsuitable for connecting to mysql via network socket on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #10 from Marek Zarychta --- (In reply to Michael Tuexen from comment #9) >sockstat -sSPtcp I have tested it on another host with the same issue. Before switching to net.inet.tcp.functions_default=freebsd and with net/freeradius3

[Bug 256657] [tcp] RACK unsuitable for connecting to mysql via network socket on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #9 from Michael Tuexen --- (In reply to Marek Zarychta from comment #8) OK, good. jails are not relevant here (this is what I expected). It would be great if you could provide the output of sockstat -sSPtcp when running both

[Bug 256657] [tcp] RACK unsuitable for connecting to mysql via network socket on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 Marek Zarychta changed: What|Removed |Added Summary|[tcp] RACK unsuitable for |[tcp] RACK unsuitable for

[Bug 256657] [tcp] RACK unsuitable for jails on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #7 from Michael Tuexen --- When your database client hangs, what is the output of sockstat -sSPtcp when running it in the jail and when running it on the host? -- You are receiving this mail because: You are on the CC list f

[Bug 256657] [tcp] RACK unsuitable for jails on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #6 from Michael Tuexen --- Another question: Does the same problem occur when running the database client and server on the host using RACK? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 256657] [tcp] RACK unsuitable for jails on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #5 from Marek Zarychta --- (In reply to Michael Tuexen from comment #2) >Could you share the commands how to reproduce that? Try to connect from the jail to the socket on the host: mysql -p -u root -h 127.0.0.1 The host has Ma

[Bug 256657] [tcp] RACK unsuitable for jails on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #4 from Michael Tuexen --- This is strange. When using nc, did you enter CTRL-D on the client side right after starting the client? This would be like in the failing trace. The client initiates a connection is terminates it wi

[Bug 256657] [tcp] RACK unsuitable for jails on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #3 from Marek Zarychta --- Created attachment 225874 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=225874&action=edit Traffic dump collected on lo0 intefrace (working fine) No, I am not able to reproduce it neither

[Bug 256657] [tcp] RACK unsuitable for jails on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 Michael Tuexen changed: What|Removed |Added CC||tue...@freebsd.org --- Comment #2

[Bug 256657] [tcp] RACK unsuitable for jails on stable/13

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 Marek Zarychta changed: What|Removed |Added CC||n...@freebsd.org Keywor

[Bug 253990] NTB driver causes panic: page fault

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253990 --- Comment #2 from Alexander Motin --- I am definitely agree that ntb->hw_info->db_count assignment in amd_ntb_init_isr() is logically incorrect. May be it could be per-instance. I have documentation not hardware for the AMD NTB, but I g

[Bug 253990] NTB driver causes panic: page fault

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253990 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org,

[Bug 255859] ipfilter/netinent: ip_nat memory leak and use-after-free

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255859 Mark Johnston changed: What|Removed |Added Status|In Progress |Closed Resolution|---

[Bug 255871] net/rtsock: Fix a use after free in update_rtm_from_rc

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255871 Mark Johnston changed: What|Removed |Added Status|In Progress |Closed Resolution|---

[Bug 254015] Panic when using bridge interface on 13.0-BETA4

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254015 --- Comment #20 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=bc6a2267fffeafd3946637607a74cfd639398f9d commit bc6a2267fffeafd3946637607a74cfd639398f9d Author:

[Bug 255069] net.link.ether.ipfw=1 leads to kernel panic under 13.0-RELEASE amd64

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255069 --- Comment #6 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=bc6a2267fffeafd3946637607a74cfd639398f9d commit bc6a2267fffeafd3946637607a74cfd639398f9d Author:

[Bug 256439] if_bridge(4): Kernel panic on FreeBSD 13.0-RELEASE: bridge_rthash

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256439 --- Comment #34 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=bc6a2267fffeafd3946637607a74cfd639398f9d commit bc6a2267fffeafd3946637607a74cfd639398f9d Author:

[Bug 241954] netgraph: Fails on concurrent node rename

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241954 --- Comment #11 from commit-h...@freebsd.org --- A commit in branch stable/11 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=4a0c1d0543afd83156b50b3f9b74c79e74cf526f commit 4a0c1d0543afd83156b50b3f9b74c79e74cf526f Author

[Bug 241954] netgraph: Fails on concurrent node rename

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241954 --- Comment #10 from commit-h...@freebsd.org --- A commit in branch stable/12 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=2def8906341231cd6b3647756c182f60d114deee commit 2def8906341231cd6b3647756c182f60d114deee Author

[Bug 256439] if_bridge(4): Kernel panic on FreeBSD 13.0-RELEASE: bridge_rthash

2021-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256439 Kubilay Kocak changed: What|Removed |Added See Also||https://reviews.freebsd.org