The short version, when I use FreeBSD 13, delivering data can take 5 minutes
for 1MB over SSH or HTTP when using IPv6. This problem does not happen with
IPv4. I installed FreeBSD 12 and Linux on that same device, neither had the
problem.
Did some troubleshooting with Linode, have ultimately rul
>
> On 13 March 2021, at 17:03, Doug Hardie wrote:
>
> I have two systems on the same ethernet. One is configured as a router, the
> other as a host. rtadvd is running on the router, rtsold on the host, and
> route6d on both. The router was up and running and I initiated tcpdump of
> ip6 p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241121
Neel Chauhan changed:
What|Removed |Added
Resolution|--- |Not Accepted
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243833
Neel Chauhan changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
Andrey V. Elsukov changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254309
Andrey V. Elsukov changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #17 from Marek Zarychta ---
(In reply to Hans Petter Selasky from comment #14)
I am sorry for borking this patch, downloaded the wrong patch (diff to the
previous diff).
The patch was applied and the system rebooted. To meet ini
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #16 from Hans Petter Selasky ---
Did you revert the previous patch?
Works fine here:
cat iflib.diff | patch -p1
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--
|diff --gi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #15 from Marek Zarychta ---
(In reply to Hans Petter Selasky from comment #12)
I am sorry, I can't test it. The patch doesn't apply on last stable/13 sources:
Rejected hunk #2.
--
You are receiving this mail because:
You are t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #14 from Hans Petter Selasky ---
Comment on attachment 223294
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223294
backtrace 1
In the debug (kgdb prompt) you can try to dump this mbuf:
print ((struct mbuf *)0xf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
Hans Petter Selasky changed:
What|Removed |Added
CC||sh...@freebsd.org
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
Hans Petter Selasky changed:
What|Removed |Added
Attachment #223301|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #11 from Marek Zarychta ---
I have been running 13.0-STABLE on this machine since 8 Feb 2021 and upgrading
once or twice a week without issues. The machine was running production code:
firewall (PF + IPFW with dummynet), HTTP pr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #10 from Mark Johnston ---
(In reply to Marek Zarychta from comment #9)
Yes, disabling LRO would be a reasonable first step. I looked at the commits
between the problematic revision and the known-good revision and nothing reall
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #9 from Marek Zarychta ---
(In reply to Hans Petter Selasky from comment #7)
Too late, the patch was applied and the new kernel is installed. I will revert
it then.
Could it be LRO issue? I have here LRO enabled on two igb(4)s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #8 from Mark Johnston ---
There's a number of similar-looking reports on stable/13. I wonder if some MFC
was missed.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #7 from Hans Petter Selasky ---
Looks like I'm wrong. m_init() clears m_nextpkt, must be something else.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
Hans Petter Selasky changed:
What|Removed |Added
Status|New |In Progress
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #6 from Hans Petter Selasky ---
Created attachment 223301
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223301&action=edit
Patch to try
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #5 from Hans Petter Selasky ---
Hi,
I looks to me like iflib's rxeof has produced an invalid chain of mbufs.
I only see one bug in there, and that is, if iflib_fixup_rx() gets a new mbuf
header, the m_nextpkt field doesn't get
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254309
--- Comment #5 from rozhuk...@gmail.com ---
igb0: flags=8863 metric 0 mtu 9000
options=4e527bb
ether ***
media: Ethernet autoselect (1000baseT )
status: active
nd6 options=9
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254309
--- Comment #4 from rozhuk...@gmail.com ---
Created attachment 223296
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223296&action=edit
log 2
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254309
--- Comment #3 from rozhuk...@gmail.com ---
Created attachment 223295
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223295&action=edit
crash log
http://www.netlab.linkpc.net/download/software/os_cfg/FBSD/13/base/usr/src/sys/amd6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
--- Comment #4 from Marek Zarychta ---
Created attachment 223294
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223294&action=edit
backtrace 1
Here's fresh backtrace
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254309
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254309
Mark Linimon changed:
What|Removed |Added
Keywords||panic
Assignee|b...@freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #3 from Aleks ---
(In reply to Marek Zarychta from comment #2)
It does happen on 13.0-RC2 too with default sysctl settings. (multipath=1)
With sysctl net.route.multipath=0 it doesn't crash. (on RC2)
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
Marek Zarychta changed:
What|Removed |Added
CC||zarych...@plan-b.pwste.edu.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #1 from Aleks ---
Same issue on Freebsd 13 RC2
13.0-RC2 #0 releng/13.0-n244684-13c22f74953: Fri Mar 12 04:05:19 UTC 2021
r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
Frr same :
frr7-7.5_1
Na
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
Mark Linimon changed:
What|Removed |Added
Keywords||panic
Assignee|b...@freeb
30 matches
Mail list logo
