[Bug 230465] ixl: not working in netmap mode

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230465 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiv

[Bug 238645] ntb: ntb_hw: use intel_ntb_printf rather than device_printf

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238645 Mark Linimon changed: What|Removed |Added Keywords|patch |IntelNetworking Assignee|

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

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiv

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

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256657 --- Comment #22 from Michael Tuexen --- (In reply to Marek Zarychta from comment #21) Will provide some notes tomorrow how to setup TCP Black Box logging. Hopefully we can figure out what the server does not like... -- You are receiving t

[Bug 256610] Kernel panic with ngtee

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256610 --- Comment #8 from Niels Bakker --- (In reply to Mark Johnston from comment #7) No crash with this patch applied while doing the same thing that used to trigger a panic. -- You are receiving this mail because: You are the assignee for th

[Bug 256610] Kernel panic with ngtee

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256610 --- Comment #7 from Mark Johnston --- Niels, are you able to test the patch from comment 4? (With kern.ipc.mb_use_ext_pgs set back to 1 of course.) -- You are receiving this mail because: You are the assignee for the bug.

[Bug 256714] Memory leaks when detaching a device

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256714 jcap...@blackberry.com changed: What|Removed |Added Attachment #225929|0 |1 is obsolete|

[Bug 256610] Kernel panic with ngtee

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256610 --- Comment #6 from John Baldwin --- Ok, I think I'm happy with m_dup always generating a mapped chain then. Presumably even if you did unmapped you'd still need to be allocating pages, etc. m_dup() already handles jumbo frames suboptimal

[Bug 256610] Kernel panic with ngtee

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256610 --- Comment #5 from Mark Johnston --- (In reply to John Baldwin from comment #4) The full stack looks like this: #8 #9 memmove_erms () at /usr/src/sys/amd64/amd64/support.S:547 #10 0x80c80f18 in m_dup (m=0xf8021e841200,

[Bug 256610] Kernel panic with ngtee

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256610 --- Comment #4 from John Baldwin --- I'm curious how this is using unmapped mbufs? Does ngtee use sendfile(2) under the hood? While we could patch m_dup(), I don't know we want to enforce the policy that the dup is always unmapped? That

[Bug 256610] Kernel panic with ngtee

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

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

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255069 Mark Johnston changed: What|Removed |Added Status|Open|In Progress Assignee|n..

[Bug 256714] Memory leaks when detaching a device

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

[Bug 256681] [route] Incorrect loopback route for aliases IP addresses

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256681 Zhenlei Huang changed: What|Removed |Added Keywords|regression | --- Comment #6 from Zhenlei Huang

[Bug 256681] [route] Incorrect loopback route for aliases IP addresses

2021-06-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256681 --- Comment #5 from Zhenlei Huang --- > So in some cases, if the loopback route is disabled and the hardware/logical > interface can not forward those packets destined for local, 'No route to > host' should be generated. Since release/8.