https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711
--- Comment #11 from Zhenlei Huang ---
Created attachment 236944
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=236944&action=edit
Draft patch
vxlan(4) vxlan_input() requires at least ETHER_HDR_LEN of mbuf.
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711
--- Comment #12 from Zhenlei Huang ---
(In reply to Alfa from comment #10)
I've test the patch on stable/13 and it works excellently. Can you please test
patch on stable/12 ?
--
You are receiving this mail because:
You are on the CC list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711
--- Comment #13 from Zhenlei Huang ---
See also: https://reviews.freebsd.org/D36794
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711
--- Comment #14 from Alfa ---
(In reply to Zhenlei Huang from comment #12)
i am currently working on FreeBSD 14.0 CURRENT 20220923 build.
Now i can test it on FreeBSD 14.0 later test it 12/stable
I removed wg-go implementation and reinstal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711
--- Comment #15 from Alfa ---
(In reply to Alfa from comment #14)
(In reply to Zhenlei Huang from comment #12)
i have tested your patch (attachment 236944) on FreeBSD 14 Current but not
worked.
I am still getting kernel: vxlan700: discard
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711
--- Comment #16 from Alfa ---
(In reply to Alfa from comment #15)
[UPDATE]
I reapplied your patch to FreeBSD 14.0 Current 20220923 and it worked perfectly
thanks for your work.
Now wireguard-kmod and vxlan works as expected.
--
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711
--- Comment #17 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=8707cb19e68128c181477d87f960182c14e15f12
commit 8707cb19e68128c181477d87f960182c14e15f12
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #110 from Dmitriy ---
(In reply to Michael Tuexen from comment #87)
Hello,
after applying of the patch named "Fix offset computation" system is currently
12 days uptime with the same workload that before patch causing the crash
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #111 from Christos Chatzaras ---
Hello,
Is it possible this patch fixes the issue in comment #36 ?
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #112 from Richard Scheffenegger ---
(In reply to Christos Chatzaras from comment #111)
Yes, this is very likely - the "fix offset" patch addresses the problematic
sequence of events, leading to this off-by-one calculation.
MAI
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
Michael Tuexen changed:
What|Removed |Added
Flags|mfc-stable13? |mfc-stable13+,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266735
Alfa changed:
What|Removed |Added
CC||burak...@outlook.com,
|
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241718
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254244
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263617
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258183
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253990
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235152
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254725
--- Comment #16 from Hans Petter Selasky ---
What version of FreeBSD did this crash happen on?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254725
--- Comment #17 from Hans Petter Selasky ---
This PR looks like it is already fixed in 13-stable. Try using a 13-stable
kernel.
--HPS
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254725
Richard Scheffenegger changed:
What|Removed |Added
Status|New |In Progress
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263445
--- Comment #34 from Richard Scheffenegger ---
I believe we can close this bug, as we haven't had any reports of issues by
those affected after updating/patching..
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
Richard Scheffenegger changed:
What|Removed |Added
Status|New |In Progress
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
Richard Scheffenegger changed:
What|Removed |Added
Status|Open|In Progress
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263445
Michael Tuexen changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
Michael Tuexen changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
Michael Tuexen changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254725
--- Comment #18 from Christos Chatzaras ---
It happened with 13.0 and 13.1. For now I have net.inet.tcp.sack.enable=0 but I
plan to enable it again after 13.2 is released to see if it's fixed. Also the
issue only happens in servers with spe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240609
Gleb Smirnoff changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241162
--- Comment #10 from Dmitry Marakasov ---
I've enabled sendfile in nginx and uwsgi on my 13.1 prod. If the panic doesn't
reproduce in a week I guess this can be closed.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266999
Kubilay Kocak changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266999
Kubilay Kocak changed:
What|Removed |Added
Flags||maintainer-feedback?(kevans
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240609
Kubilay Kocak changed:
What|Removed |Added
Flags|maintainer-feedback?(glebiu |maintainer-feedback+,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266999
--- Comment #2 from Kyle Evans ---
(In reply to Seyed Pouria Mousavizadeh Tehrani from comment #0)
error == 17, EEXIST
Across the entire system, can you describe how you create and use tun
interfaces? Are you just letting openvpn create t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266999
--- Comment #3 from Seyed Pouria Mousavizadeh Tehrani
---
I have two net/ocserv applications in separate jails and give them unhide
access to the "/dev/tun*" with devfs. The ocserv will use the /dev/tun special
control device file to creat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266999
--- Comment #4 from Kyle Evans ---
So, to be clear:
- openvpn-client is using tun257 and tun258, it is in its own vnet.
- The two ocserv jails also each have their own vnets, and use whatever tun
interfaces they get from opening /dev/tun
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266999
--- Comment #5 from Seyed Pouria Mousavizadeh Tehrani
---
- openvpn-client is using tun257 and tun258, it is in its own vnet:
No. openvpn-clients are in *host* and not in *jail* so their are not using
vnet.
host rc.conf:
"""
openvpn_cli
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253251
--- Comment #7 from Christian Gutzler ---
Any development on this?
--
You are receiving this mail because:
You are the assignee for the bug.
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=121774
Graham Perrin changed:
What|Removed |Added
Keywords||crash
--- Comment #6 from Graham P
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=138782
Graham Perrin changed:
What|Removed |Added
Keywords||crash
--- Comment #9 from Graham P
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184311
Graham Perrin changed:
What|Removed |Added
Keywords||crash
--- Comment #9 from Graham P
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266048
Anthony Capone changed:
What|Removed |Added
CC||cap...@cap1.net
--- Comment #2 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256820
--- Comment #6 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=3b1dbf19f9c051a325774ba5c0d7cc460cc82c7f
commit 3b1dbf19f9c051a325774ba5c0d7cc460cc82c7f
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256820
Koichiro Iwao changed:
What|Removed |Added
Flags|mfc-stable13? |mfc-stable13+
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256820
--- Comment #7 from commit-h...@freebsd.org ---
A commit in branch stable/12 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=a0e9703f57cb2ba2bcf8a765f42f8fe702a3cca8
commit a0e9703f57cb2ba2bcf8a765f42f8fe702a3cca8
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256820
Koichiro Iwao changed:
What|Removed |Added
Flags|mfc-stable12? |mfc-stable12+
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266048
--- Comment #3 from Andrey V. Elsukov ---
Created attachment 237452
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=237452&action=edit
proposed patch
I think for now we can use the same solution as here:
https://git.dpdk.org/dpdk
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266048
--- Comment #4 from Franco Fichtner ---
We were testing https://github.com/opnsense/src/commit/4a788be44e0 yesterday
and it was confirmed working. Your patch is shorter, happy to see it committed!
Cheers,
Franco
--
You are receiving thi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Gleb Smirnoff changed:
What|Removed |Added
CC||gleb...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #2 from Richard Scheffenegger ---
Can you please provide more context around the traces?
Did you capture on the client side, or on the server side?
It appears, that the capture was performed on the client side, with LRO enabled
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #3 from Keyong ---
(In reply to Gleb Smirnoff from comment #1)
The freeBSD deployed on the physical machine.
The software used to send the data is "truenas".
Thanks
Keyong
--
You are receiving this mail because:
You are the a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #4 from Keyong ---
(In reply to Richard Scheffenegger from comment #2)
The packet captured on both client and server.
During the last reproduce this issue, the client/server LRO/TSO with default
setting, I didn't change that.
T
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #5 from Richard Scheffenegger ---
Where are the two independent packet traces, if you traced on both client and
server at the same time?
Also, disabling SACK will lead to much worst packet loss recovery performance,
while also
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Keyong changed:
What|Removed |Added
Attachment #235649|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #7 from Keyong ---
Created attachment 237477
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=237477&action=edit
Server side packet trace
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #8 from Keyong ---
(In reply to Richard Scheffenegger from comment #5)
Thanks for your detail analyze, sorry to forget attach the client side packet
trace, attached both sides now.
--
You are receiving this mail because:
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #9 from Richard Scheffenegger ---
ClientSide:
2 10.234.1.9 35249 229 11584 8
72053392291 385714934591419632206729401031568921410043220839
398170924830381008236919388657879560
3 10.234.1.9 46833 229 4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #10 from Richard Scheffenegger ---
There seems to be a discrepancy in the TSO vs LRO payload bytes (maybe my
script is broken?):
Server:
2 10.234.1.9 35249 229 15928 11
72053392291 38571493459141963220672940103156
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256820
Koichiro Iwao changed:
What|Removed |Added
CC||h...@freebsd.org
--- Comment #8 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #11 from Keyong ---
(In reply to Richard Scheffenegger from comment #10)
Yes, the capture created before issuing the read.
Because the issue was not reproduced 100%, so need to capture with a long time,
the origin packet was to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #13 from Keyong ---
(In reply to Hans Petter Selasky from comment #12)
Thanks for your information.
The client Linux kernel was not the lastest.
With the SACK disabled I haven't reproduce this issue. Only can reproduce this
issu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #15 from Michael Tuexen ---
Is it possible to test if the problem does still exists in stable/13?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #16 from Richard Scheffenegger ---
My script was not using correctly calculating the index when extracting the
payload bytes (vs. nibbles).
Server:
2 10.234.1.9 35249 229 15928 11
0x71d1c76e360xb735f725570xbad512b35a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #17 from Richard Scheffenegger ---
1448 byte chunks between server and client align perfectly until server frame
#51 (5 chunks: 0xb23ee730dd0xc2fd29b2eb0xbe27bbf1be0xb829e51fdc
0xbc5b20682b) and client frame #48 (
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Richard Scheffenegger changed:
What|Removed |Added
Status|New |Open
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #18 from Richard Scheffenegger ---
For completeness, the awk script with proper indexing:
cat output | awk '
//{
fr=int($5/1448);
if ((fr*1448 == $5) && (fr > 0)) {
print $1" "$2" "$3" "$4" "$5"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Michael Zhilin changed:
What|Removed |Added
CC||miz...@freebsd.org
Seve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #20 from Richard Scheffenegger ---
This behavior was likely introduced by 0533fab89e37caab886568df88d9f939e85eeb6c
D28634 (Mar 25 2021), but addressed with
c21b7b55bea2cc2bf3b420c70a9018e703ed6f00 D36046 (Aug 31 2022).
Looking
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
Richard Scheffenegger changed:
What|Removed |Added
Status|Open|In Progress
Prio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #21 from Keyong ---
Many thanks to all provide helps!
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #22 from Richard Scheffenegger ---
(In reply to Keyong from comment #21)
Do you know, what devices are on the path between your fbds NFS server and the
Linux client?
As you can see, the ACKs sent by the Linux client are correc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #23 from Keyong ---
(In reply to Richard Scheffenegger from comment #22)
As I remember, there wasn't any specify middlebox between server and client,
but the client was deployed in a hypervisor with VM, the hypervisor is KVM. An
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #24 from Michael Tuexen ---
(In reply to Richard Scheffenegger from comment #22)
Hi Richard,
why is it important how/why the reordering of ACKs observed by FreeBSD
happened? We should make sure that FreeBSD behaves correctly in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252165
--- Comment #26 from Hans Petter Selasky ---
These issues are not forgotten. It just takes a while to find good and generic
solutions. Maybe all MII bus code should be executed for the same thread?
Would remove the need for depending on lo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230807
--- Comment #15 from Eugene Grosbein ---
Any updates on the topic? There are reports that alc(4) is not stable for
Killer E2200 gigabit ethernet controller in 13.1
--
You are receiving this mail because:
You are on the CC list for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230807
Cheburashka changed:
What|Removed |Added
CC||snake05...@mail.ru
--- Comment #16 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230807
--- Comment #17 from Mark Millard ---
(In reply to Cheburashka from comment #16)
I've seen similar OS context-switching behavior with the
ThreadRipper 1950X X399 AORUS gaming 7 I use that has an
E2500. Complete power off-then-on is the onl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246706
Eugene Grosbein changed:
What|Removed |Added
Resolution|--- |Overcome By Events
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246706
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206165
Marek Zarychta changed:
What|Removed |Added
CC||n...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206165
Benedict Reuschling changed:
What|Removed |Added
CC||b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206165
Graham Perrin (non-committing) changed:
What|Removed |Added
CC||grahamper...@gmail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206165
--- Comment #8 from Graham Perrin (non-committing) ---
> … add the URL of the review to the See also: field. …
For clarity, I mean:
* your D37096
* not my D37086
--
You are receiving this mail because:
You are on the CC list for th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206165
--- Comment #9 from Graham Perrin (non-committing) ---
Re: comment #7
> aim for the #bugs channel.
Correcting myself:
the #freebsd-bugs channel.
Apologies for the noise.
--
You are receiving this mail because:
You are on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857
--- Comment #3 from benoitc ---
any news ?
--
You are receiving this mail because:
You are the assignee for the bug.
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857
--- Comment #4 from Zhenlei Huang ---
(In reply to benoitc from comment #0)
>I have setup 3 nodes on a fresh Freebsd 13.1-RELEASE-p1. They have the same
>gateway
> and IPS are in same /64. All 3 nodes are on the same switch (mikrotik) and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857
--- Comment #5 from Zhenlei Huang ---
> Pings start to work when the interface is put in promiscuous mode or an IPV4
> address is set.
> The card is an HPE Eth 10/25Gb 2p 621SFP28 Adptr:
> https://support.hpe.com/hpesc/public/docDisplay?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857
--- Comment #6 from Zhenlei Huang ---
(In reply to benoitc from comment #1)
I'm not sure whether the interface is not properly initialized or not, but you
can try to change the MTU (maximum is 9000 as defined in the driver's source
code),
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265588
--- Comment #25 from Michael Zhilin ---
Hi,
Is it possible to backport fix to releng/13.1? I suppose it make sense to fix
it in release version to improve user experience.
Thanks!
--
You are receiving this mail because:
You are the assi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
ykla changed:
What|Removed |Added
CC||ykla...@gmail.com
--- Comment #103 from ykl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Marek Zarychta changed:
What|Removed |Added
Resolution|--- |Overcome By Events
St
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Marek Zarychta changed:
What|Removed |Added
Status|Closed |Open
Resolution|Overcome
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261711
Graham Perrin changed:
What|Removed |Added
Assignee|ports-b...@freebsd.org |k...@freebsd.org
See Als
501 - 600 of 13467 matches
Mail list logo
