https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981
SJ changed:
What|Removed |Added
CC||sa...@rbrd.io
--- Comment #24 from SJ ---
Ex
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981
--- Comment #25 from Kurt Jaeger ---
(In reply to SJ from comment #24)
Can you update to 13.1, as it contains some fixes for bnxt ?
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981
--- Comment #26 from SJ ---
(In reply to Kurt Jaeger from comment #25)
Done!
% uname -a
FreeBSD foo 13.1-RELEASE FreeBSD 13.1-RELEASE
% kldstat
Id Refs AddressSize Name
1 27 0x8020 1f30590 kernel
21 0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981
--- Comment #27 from Kurt Jaeger ---
(In reply to SJ from comment #26)
If the interfaces can be made to appear, are they usable ?
Is the performance appropriate ?
Or do they show, but fail to work ?
--
You are receiving this mail because
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981
--- Comment #28 from SJ ---
(In reply to Kurt Jaeger from comment #27)
After some testing, I can confirm that they show, but fail to work. When
configuring one of the interfaces to use DHCP, it doesn't obtain anything,
showing the IP 0.0.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981
--- Comment #29 from Kurt Jaeger ---
I tested 13.1-RC1 with the BCM57414. I have no BCM57416 to test 8-(
--
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=245981
--- Comment #30 from SJ ---
(In reply to Kurt Jaeger from comment #29)
As per #20, it seems like firmware version 21.65.33.33 may work. Whether or not
it'll let me upgrade is a different thing altogether! It'll be tomorrow or
Monday before
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263986
Tatsuki Makino changed:
What|Removed |Added
CC||tatsuki_mak...@hotmail.com
--- Co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263379
--- Comment #16 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=6835ace580917ec512eb96cf9c456f4acc161247
commit 6835ace580917ec512eb96cf9c456f4acc161247
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263379
--- Comment #17 from commit-h...@freebsd.org ---
A commit in branch stable/12 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=6aaf8a8b1bcf500aa7342043d43007ff9c52cd65
commit 6aaf8a8b1bcf500aa7342043d43007ff9c52cd65
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193953
--- Comment #15 from Marek Zarychta ---
Committed to main https://cgit.freebsd.org/src/commit/?id=f2ab9160
Thanks, we are looking forward to MFC.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193953
Marek Zarychta changed:
What|Removed |Added
CC||w...@freebsd.org
Fla
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263831
Hiroki Sato changed:
What|Removed |Added
Status|New |In Progress
Assignee|n...@
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Marek Zarychta changed:
What|Removed |Added
CC||n...@freebsd.org
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Marek Zarychta changed:
What|Removed |Added
Summary|seting |setting
|net.in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
St
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Michael Tuexen changed:
What|Removed |Added
Summary|setting |[tcp] setting
|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263756
Natalino Picone changed:
What|Removed |Added
CC||natalino.picone@nozominetwo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264006
--- Comment #1 from Jiahao LI ---
Created attachment 234058
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=234058&action=edit
Fix patch following other drivers code sequence
Updating the previous patch.
Following other drivers'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash, needs-qa
Severity
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
demus...@gmail.com changed:
What|Removed |Added
CC||demus...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224961
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264114
Kubilay Kocak changed:
What|Removed |Added
CC||n...@freebsd.org
Assigne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264114
--- Comment #3 from Nick Briggs ---
It would be a much better UX if the wireguard kmod if_wg.ko were tagged such
that the kernel module loader noticed that it was not compatible with the new
kernel.
The virtualbox module seems to be coded
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264114
--- Comment #4 from Bernhard Froehlich ---
Okay I keep this PR open to mark all future PRs as duplicates.
The reason for the panic is that all packages are build on 13.0 which works
fine for userland packages because they are compatible wi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264114
lb...@disroot.org changed:
What|Removed |Added
CC||lb...@disroot.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264114
Marek Zarychta changed:
What|Removed |Added
CC||zarych...@plan-b.pwste.edu.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264114
--- Comment #7 from Bernhard Froehlich ---
(In reply to Marek Zarychta from comment #6)
No that does not work. Compatibility only works in one direction. Packages are
build with the oldest supported version on that branch which is correct.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #2 from Michael Tuexen ---
The panic happens on arm64, but not amd64. It does happen when using clang14
(most recent version in the main tree), it does not happen when using clang13.
I also does not happen using clang14 when for
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=264094
--- Comment #3 from Marek Zarychta ---
Thank you for digging into this. It looks like a clang14 flaw. Please see: bug
264021 and probably also bug 264115.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Jessica Clarke changed:
What|Removed |Added
CC||jrt...@freebsd.org
--- Comment #4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #5 from Jessica Clarke ---
Well, that composed with
https://github.com/llvm/llvm-project/commit/4450a2a23df0e7081ca7fee3ec641774afedc2bc
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #6 from Jessica Clarke ---
To confirm, you are using cc_htcp.ko rather than compiling it into your kernel?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #7 from Marek Zarychta ---
(In reply to Jessica Clarke from comment #6)
>To confirm, you are using cc_htcp.ko rather than compiling it into your kernel?
Of course. Good idea. I didn't know it is even possible to build the kerne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #8 from Jessica Clarke ---
(In reply to Marek Zarychta from comment #7)
In the kernel should work as it's prepared for those kinds of optimisations,
but kernel modules should not, as they rely on the indirection persisting and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
John F. Carr changed:
What|Removed |Added
CC||j...@mit.edu
--- Comment #9 from Jo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264114
Kyle Evans changed:
What|Removed |Added
CC||kev...@freebsd.org
--- Comment #8 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #10 from Jessica Clarke ---
(In reply to John F. Carr from comment #9)
The optimisation is correct for non-preemptible symbols. It's not correct for
preemptible symbols (or hacks like vnet/dpcpu that rely on symbol and
relocati
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #11 from Michael Tuexen ---
(In reply to Jessica Clarke from comment #6)
I just tested that the problem does not show up if you build the CC module in
the kernel using the CC_HTCP kernel option.
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Michael Tuexen changed:
What|Removed |Added
Assignee|tue...@freebsd.org |b...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264059
--- Comment #9 from Hans Petter Selasky ---
Ping
--HPS
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264059
--- Comment #10 from crb ---
Sorry, I thought I left a message and closed this. I was, indeed, missing the
module you suggested. When I loaded that the machine started working. Thank
you!
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264059
Hans Petter Selasky changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Ope
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263824
--- Comment #7 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=7e6e22aab6b993e42328bafe0f64ee14a2b7c43c
commit 7e6e22aab6b993e42328bafe0f64ee14a2b7c43c
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263824
Mike Karels changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981
--- Comment #31 from SJ ---
I couldn't find a version matching 21.65.33.33, but downgraded the NIC firmware
to 21.60.22.11 and everything worked fine after loading the kernel module.
Tried upgrading to 22.00.07.60 again after that and can c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #13 from Michael Tuexen ---
Just another data point: Disabling VNET also works around the problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #14 from Jessica Clarke ---
Yes, it's a problem with how VNET (and DPCPU) are designed
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264193
Kubilay Kocak changed:
What|Removed |Added
Status|New |Open
Flags|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264191
Kubilay Kocak changed:
What|Removed |Added
CC||hsela...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258923
Kubilay Kocak changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264191
--- Comment #2 from Kubilay Kocak ---
See also base 5a7de2b42caf via bug 258923 apologies.
--
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=264179
Mark Linimon changed:
What|Removed |Added
Keywords||IntelNetworking, regression
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264179
Kubilay Kocak changed:
What|Removed |Added
Blocks||264030
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Kubilay Kocak changed:
What|Removed |Added
Severity|Affects Many People |Affects Some People
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264191
--- Comment #3 from Bryan Drewery ---
(In reply to Kubilay Kocak from comment #2)
None of this is a recent regression. It is design flaws.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
--- Comment #16 from Michael Tuexen ---
(In reply to Kubilay Kocak from comment #15)
I think I gave all information I can provide. I'm not familiar with the
internals for clang...
--
You are receiving this mail because:
You are on the CC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264094
Kubilay Kocak changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264179
--- Comment #2 from Yasuhiro Kimura ---
(In reply to Kubilay Kocak from comment #1)
> - Can you confirm boot behaviour is OK on 12.1-RELEASE ?
Do you mean 12.3-RELEASE? If so, same hangup happens with it.
> - Is the system able to boot s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264179
--- Comment #3 from Yasuhiro Kimura ---
According to the suggestion in freebsd-stable ML, I added
'hint.em.1.disabled=1' to /boot/loader.conf and then 13.1-RELEASE boots
successfully.
--
You are receiving this mail because:
You are on the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263756
Ryan Steinmetz changed:
What|Removed |Added
CC||z...@freebsd.org
--- Comment #4 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263756
--- Comment #5 from Natalino Picone ---
(In reply to Ryan Steinmetz from comment #4)
This is not working as the 12.3 intel driver contains a bug.
ifconfig reports that features have been disabled, but they are not.
See https://reviews.free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263756
--- Comment #6 from Ryan Steinmetz ---
(In reply to Natalino Picone from comment #5)
My use case is closer to what s...@42.org described--where I have vlan
interfaces created.
I don't think my situation is identical to what you reported, b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264248
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264248
--- Comment #1 from Hans Petter Selasky ---
Have you checked if a fix exist in Linux?
--
You are receiving this mail because:
You are the assignee for the bug.
Kubilay Kocak has asked freebsd-net (Nobody)
for maintainer-feedback:
Bug 264257: Panic: Fatal trap 12: page fault while in kernel mode (if_io_tqg_4)
- m_copydata ... at /usr/src/sys/kern/uipc_mbuf.c:659
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
Kubilay Kocak changed:
What|Removed |Added
CC||hsela...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #3 from iron.ud...@gmail.com ---
(In reply to Michael Tuexen from comment #2)
Unfortunately I don't know how to reproduce this bug. The server was working a
week or so without any problem. Today it suddenly panicked and restarte
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #4 from iron.ud...@gmail.com ---
(In reply to Michael Tuexen from comment #2)
Do you need all of my sysctls from /etc/sysctl.conf and /boot/loader.conf?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264179
--- Comment #4 from Yasuhiro Kimura ---
Now boot succeeds with 13.1-RELEASE and `pciconf -lv` gets following result.
yasu@maybe[1028]% pciconf -lv
hostb0@pci0:0:0:0: class=0x06 rev=0x05 hdr=0x00 vendor=0x8086
device=0x4630 subvend
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #5 from John Baldwin ---
Looks like it walked off the end of the mbuf chain as it tried to copy one byte
too many. You could try going up to frame 8 (tcp_output) to see if the
arguments passed to m_copydata() are still around (
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #6 from iron.ud...@gmail.com ---
(In reply to John Baldwin from comment #5)
Oh...I'm not sure that I can do it by myself. I'm not so expirianced in
debugging. Can I send you compressed core dump file?
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #7 from John Baldwin ---
Hmm, unfortunately it would need to be the contents of /boot/kernel and
/usr/lib/debug/boot/kernel along with the vmcore. However, if you can stick
those all in a tarball I can take a look at them. It
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #8 from iron.ud...@gmail.com ---
(In reply to John Baldwin from comment #7)
Emailed you link on archive.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234073
--- Comment #18 from benoitc ---
is there anything that can be done for it ? Any update needed? It's kind of
suprising nobody came with a solution in 3 years on such obvious issue.
--
You are receiving this mail because:
You are the assig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234073
--- Comment #19 from benoitc ---
is there anything that can be done for it ? Any update needed? It's kind of
suprising nobody came with a solution in 3 years on such obvious issue.
--
You are receiving this mail because:
You are the assig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #9 from Michael Tuexen ---
(In reply to iron.udjin from comment #8)
You might also send the link to me (tue...@freebsd.org) and Richard
(rsch...@freebsd.org), if you are willing to do so.
--
You are receiving this mail because
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #10 from iron.ud...@gmail.com ---
(In reply to Michael Tuexen from comment #9)
Done.
--
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 #11 from Michael Tuexen ---
(In reply to iron.udjin from comment #10)
Thanks! I could download the tarball and will also have a look at it.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264114
--- Comment #9 from Bernhard Froehlich ---
So far no response from portmgr@ but I have created a patch similar to what was
done in virtualbox-ose-kmod to avoid that the kernel module can be loaded on a
kernel with a different minor version.
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=264191
Conrad Meyer changed:
What|Removed |Added
Flags|maintainer-feedback?(cem@fr |
|eebsd.org)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234073
Kubilay Kocak changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062
Kubilay Kocak changed:
What|Removed |Added
Summary|ix(4): sr-iov virtual |ix(4): SR-IOV virtual
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062
Kubilay Kocak changed:
What|Removed |Added
CC||n...@freebsd.org
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263568
Kubilay Kocak changed:
What|Removed |Added
Keywords||IntelNetworking
Priority
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200836
Kubilay Kocak changed:
What|Removed |Added
Component|kern|bin
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232472
Kubilay Kocak changed:
What|Removed |Added
Assignee|virtualizat...@freebsd.org |n...@freebsd.org
C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232472
Kubilay Kocak changed:
What|Removed |Added
Summary|ixgbe(4): Hyper-V Guest |ixgbe(4): SR-IOV passthru
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239849
Kubilay Kocak changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Summary|INTEL
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232472
--- Comment #5 from Kubilay Kocak ---
*** Bug 239849 has been marked as a duplicate of this bug. ***
--
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=253620
--- Comment #2 from Alexander V. Chernikov ---
I'll close this PR on Jun 5 if there are no other questions.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258528
--- Comment #1 from Alexander V. Chernikov ---
Sorry for the belated reply. Were there any other similar crashes after this
one?
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264248
Hans Petter Selasky changed:
What|Removed |Added
Assignee|n...@freebsd.org |hsela...@freebsd.org
--
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232472
Kubilay Kocak changed:
What|Removed |Added
Keywords||feature
Summary|ixgbe(4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232472
Kubilay Kocak changed:
What|Removed |Added
Attachment #219194||maintainer-approval?(freebs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263568
Kubilay Kocak changed:
What|Removed |Added
CC||e...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232472
Kubilay Kocak changed:
What|Removed |Added
Flags||maintainer-feedback?(kbowli
1 - 100 of 13467 matches
Mail list logo
