https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290098
--- Comment #10 from Alexander Ziaee ---
(In reply to mario felicioni from comment #9)
> What's the difference between 15-STABLE and stable/15 ?
stable/15 is the name of the branch containing the code. 15-STABLE is the name
of snapshot re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290098
--- Comment #13 from Bakul Shah ---
folks, please discuss stuff irrelevant to this bug report elsewhere. Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290098
--- Comment #5 from mario felicioni ---
I pressed ENTER and this is what happened :
https://ibb.co/j9LxXLVG
more messages appeared,but now it is frozen on the last one and it is asking a
lot of resources to my machine.
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290098
Mark Linimon changed:
What|Removed |Added
Keywords||crash
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290044
--- Comment #1 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=534aec00976c18c4c4b485b2fade9d5f33de89c8
commit 534aec00976c18c4c4b485b2fade9d5f33de89c8
Author:
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=283375
Michael Tuexen changed:
What|Removed |Added
Status|Open|Closed
Assignee|virtual
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283375
--- Comment #3 from Michael Tuexen ---
(In reply to Michael Tuexen from comment #2)
I am closing this, since it should be fixed by
https://cgit.FreeBSD.org/src/commit/?id=187ee62c71f2be62870f26ae98de865e330121be.
This has been MFCed to stab
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268794
--- Comment #18 from Andrey Lanin ---
After that patch https://reviews.freebsd.org/D52781 has been applied it
started working -
https://forums.FreeBSD.org/threads/bhyve-vm-stuck-when-passthru-enabled.92854/post-719648
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288848
mario felicioni changed:
What|Removed |Added
CC||marietto2...@gmail.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288848
Corvin Köhne changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289848
Bug ID: 289848
Summary: Enable by default BHYVE_SNAPSHOT
Product: Base System
Version: 16.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270966
--- Comment #24 from Chuck Tuffli ---
I'm seeing this on 14.3-RELEASE-p3 with a AMD Ryzen Threadripper 3970X 32-Core
Processor
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267620
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
St
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=26
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289400
Bug ID: 289400
Summary: bhyve(8) VM boot aborts with "Synchronous Abort" on
boot on ARM64 Honeycomb LX2 Host
Product: Base System
Version: 15.0-CURRENT
Hardware: arm6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287326
Kyle Evans changed:
What|Removed |Added
CC||corv...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268428
Christos Margiolis changed:
What|Removed |Added
CC||chris...@freebsd.org
--- Comm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287326
--- Comment #2 from Corvin Köhne ---
The warnings on stdout are generated by iasl when converting ASL, created by
bhyve, into AML. The ASL generated by bhyve was copied from QEMU and at least
some of those issues are intended to workaround
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287326
--- Comment #3 from Roman Bogorodskiy ---
(In reply to Corvin Köhne from comment #2)
> If I get it correctly, a FreeBSD guest works fine while an Ubuntu guest fails
> to boot? I would try the following:
Yes, that's correct.
> 1. Enable
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25
Corvin Köhne changed:
What|Removed |Added
CC||corv...@freebsd.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289471
Michael Dexter changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289400
--- Comment #3 from Michael Dexter ---
Sorry I was not clear and I have tried this several more times:
For my initial smoke test of a VM with an months-old version of 15.0-CURRENT,
the VM booted, but would boot when attempting to boot it a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289471
--- Comment #3 from John Baldwin ---
(In reply to Michael Dexter from comment #2)
No. AMD64 originally used statically allocated arrays, e.g.:
struct vm {
...
struct vcpu vm_vcpus[16];
};
This is why a limit of 16 was hardcoded.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289471
John Baldwin changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25
Mark Linimon changed:
What|Removed |Added
Keywords||crash
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289400
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #2 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289471
--- Comment #2 from Michael Dexter ---
I recall AMD64 having 16 explicitly set and the allocations becoming
inefficient as the vCPU count went up. Is this not the case on ARM64?
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289471
Bug ID: 289471
Summary: bhyve ARM64 16 vCPU Limit
Product: Base System
Version: 15.0-STABLE
Hardware: arm64
OS: Any
Status: New
Severity: Affects Ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289400
--- Comment #1 from Michael Dexter ---
Testing on 15.0-ALPHA1 with a 15.0-ALPHA1 UFS VM-IMAGE to allow for the default
256M RAM allocation:
U-Boot 2024.07 (Aug 23 2025 - 01:17:11 +)
DRAM: 256 MiB
"Synchronous Abort" handler, esr 0x02
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221462
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
St
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283375
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277559
Mark Linimon changed:
What|Removed |Added
Status|Open|In Progress
--
You are receiving t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252227
Mark Linimon changed:
What|Removed |Added
Status|Open|In Progress
--
You are receiving t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288873
Hayzam Sherif changed:
What|Removed |Added
Summary|Windows 11 VM with GPU |Windows 11 VM hangs on boot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207885
--- Comment #4 from Graham Perrin ---
Re: comment 0
> https://www.virtualbox.org/ticket/15232
Closed (obsolete) 2020-02-26.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207885
--- Comment #3 from Graham Perrin ---
Thanks,
(In reply to Michael Gmelin from comment #2)
Oracle documentation presents things slightly differently.
Troubleshooting /
Running Legacy Guest OSs /
IDE/SATA Errors on Guest OS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274051
--- Comment #8 from Kyle Evans ---
(In reply to Marcin Cieślak from comment #7)
Note that bhyveload(8) is just the (FreeBSD) loader part of bhyve, you need
bhyve(8) to actually drive the machine after it has finished. Typically it
would b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271134
Marcin Cieślak changed:
What|Removed |Added
CC||sa...@saper.info
--- Comment #11
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271134
--- Comment #12 from Marcin Cieślak ---
troff:bhyve.8:528: warning [p 5, 3.2i]: cannot break line
troff:bhyve.8:862: warning [p 8, 0.5i]: cannot break line
troff:bhyve.8:963: warning [p 8, 11.0i]: cannot break line
as of
https://cgit.freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274051
--- Comment #9 from Kyle Evans ---
(In reply to Kyle Evans from comment #8)
To clarify: this is one series of events. bhyveload(8) loads the machine once,
then bhyve(8) executes (as you had found). You would need to destroy and redo
the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274051
Marcin Cieślak changed:
What|Removed |Added
CC||sa...@saper.info
--- Comment #7 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274051
--- Comment #10 from Marcin Cieślak ---
Thank you. Sorry for noise.
Should have used the handbook - the man pages didn't provide me any clue.
("What is the default bootrom?!")
Coming from Xen or qemu, this was confusing. Thank you again.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=26
--- Comment #1 from dw...@infradead.org ---
I did manage to get this working with /usr/share/examples/bhyve/vmrun.sh
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288848
R Williams changed:
What|Removed |Added
CC||r...@ross-williams.net
--- Comment #6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
Michael Osipov changed:
What|Removed |Added
CC||michael.osi...@siemens.com
--- Co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288873
--- Comment #1 from Hayzam Sherif ---
I've been playing around with Windows 10 with PCI passthrough devices and I am
seeing similar problems. I got around 2 crashes at different points of the
installation. It is not as violent though, I can
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268794
Ahmad Khalifa changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288873
Ahmad Khalifa changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268794
Andrey Lanin changed:
What|Removed |Added
CC||lettergrab...@yandex.ru
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=26
Bug ID: 26
Summary: bhyve fails to start Fedora guest
Product: Base System
Version: 14.3-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Aff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25
dw...@infradead.org changed:
What|Removed |Added
Hardware|Any |amd64
--
You are receiving t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25
--- Comment #1 from dw...@infradead.org ---
Host system is a Haswell running Fedora 41 (6.13.8 kernel). Please let me know
what other details would be useful.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=25
Bug ID: 25
Summary: System locks up when starting a bhyve guest under
Linux/KVM
Product: Base System
Version: 14.3-RELEASE
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288873
Bug ID: 288873
Summary: Windows 11 VM with GPU passthrough hangs on boot when
using more than one vCPU
Product: Base System
Version: 14.3-RELEASE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288848
--- Comment #5 from Vincent ---
+
+static int
+nvidia_gpu_init(struct pci_devinst *const pi, nvlist_t *const nvl __unused)
+{
+ pci_set_cfgdata8(pi, PCIR_INTPIN, 1);
+
+ return (0);
+}
+
+static struct passthru_dev nvidia_gpu =
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288848
--- Comment #4 from Vincent ---
I applied the patches against 14.3 and can confirm it works! I only had to do a
minor change to the Makefile. Thanks again Corvin!
--- 8< ---
diff --git a/usr.sbin/bhyve/Makefile b/usr.sbin/bhyve/Makefile
in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288848
--- Comment #3 from Vincent ---
Thanks a lot Corvin, will check your changes against 14.3 today.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288848
Corvin Köhne changed:
What|Removed |Added
CC||corv...@freebsd.org
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288848
Tomoaki AOKI changed:
What|Removed |Added
CC||junch...@dec.sakura.ne.jp
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288848
Bug ID: 288848
Summary: bhyve GPU passthru for NVIDIA not working
Product: Base System
Version: 14.3-STABLE
Hardware: amd64
OS: Any
Status: New
Seve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288444
Bakul Shah changed:
What|Removed |Added
CC||ba...@iitbombay.org
--- Comment #3 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288817
--- Comment #2 from Mark Millard ---
Can(/does?) the context have misc/compat14x involved?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288817
Mark Millard changed:
What|Removed |Added
CC||marklmi26-f...@yahoo.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288817
Mark Linimon changed:
What|Removed |Added
Keywords||regression
Assignee|b...@
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #44 from Colin Percival ---
I vaguely recall that another VM system implemented 0x4010 on the basis of
"it's an unofficial standard now". Maybe qemu? Credit goes to Alex Graf for
making me aware of this anyway. A few year
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #43 from dw...@infradead.org ---
I suspect Linux doesn't use that because it was only ever *proposed* as a
generic standard (by VMware) in https://lkml.org/lkml/2008/10/1/246 and seemed
to get shot down? It never actually got ado
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #42 from Colin Percival ---
Ever since 4a432614f68cf35879dbb4ebef089f5b8db95334 (January 2022) we've been
querying the 0x4010 CPUID leaf which is set by EC2. Oddly Linux wasn't
using that leaf last time I checked.
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #41 from dw...@infradead.org ---
But wait... why are you even calibrating the TSC against the PIT in the first
place? KVM *tells* you the frequency of the TSC!
I take it back... slightly. You are allowed to use the *frequency* f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256781
--- Comment #40 from dw...@infradead.org ---
Apologies for not confirming sooner. Yes, this was due to a bug in the PIT
implementation. The PIT counter counts down, and the interrupt was supposed to
fire when it reaches zero and wraps back t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276734
Michael Osipov changed:
What|Removed |Added
CC||micha...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288444
Shawn Webb changed:
What|Removed |Added
CC||shawn.w...@hardenedbsd.org
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
--- Comment #23 from Michael Osipov ---
(In reply to ek from comment #22)
Thanks for the confirmation.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288444
Mark Johnston changed:
What|Removed |Added
Status|New |Open
--- Comment #1 from Mark John
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
--- Comment #21 from Konstantin Belousov ---
(In reply to John Baldwin from comment #19)
Sure it is not obvious functionality, but in theory vmm can intercept #UD,
parse the faulting instruction, and calculate the set it belongs to.
If this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288444
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualization@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
Michael Osipov changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #19 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203643
ShengYi Hung changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288308
Chuck Tuffli changed:
What|Removed |Added
Assignee|virtualization@FreeBSD.org |ch...@freebsd.org
--- Comment #7 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288308
--- Comment #6 from Michel Depeige ---
No worries, my wording wasn't the best as well.
I can test the new bhyve version for you, and the target version is 14.3
That being said I've already buildworld/installworld on my lab machine with a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288308
--- Comment #5 from Chuck Tuffli ---
Apologies for not wording those comments better. If I post a new version of
bhyve(4) which includes the change you cited in SmartOS, would you be able to
test if that version allows the various Windows V
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288308
--- Comment #4 from Michel Depeige ---
Reproduced the issue on a lab machine with the following hardware:
CPU: AMD EPYC 7262 8-Core Processor (3194.15-MHz K8-class CPU)
The smartos fixes the issues, although my knowledge
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288308
--- Comment #3 from Chuck Tuffli ---
Whoops, forgot to mention that the xmsr.c file in FreeBSD's bhyve lives in the
usr.sbin/bhyve/amd64/
directory.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288308
Chuck Tuffli changed:
What|Removed |Added
CC||ch...@freebsd.org
--- Comment #2 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288308
--- Comment #1 from Michel Depeige ---
Ignore previous information about Windows 2022, error on my test script, the
issue is reproductible with 2019, 2022 and 11.
Probably the same issue as here:
https://smartos.org/bugview/OS-8008
Relate
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
--- Comment #18 from Konstantin Belousov ---
(In reply to Michael Osipov from comment #17)
I am not sure what did you expected to see.
Guest exceptions of any kind (#UD included) are really normal events that must
be reflected to guest. Th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288308
Bug ID: 288308
Summary: bhyve + Windows 2025 freezes with rdmsr to register
0xc0010114 error on AMD Zen4
Product: Base System
Version: 14.3-RELEASE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
--- Comment #17 from Michael Osipov ---
(In reply to Michael Osipov from comment #16)
Enabled, rebooted. Nothing in the vm log, dmesg, messages.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
--- Comment #16 from Michael Osipov ---
(In reply to Konstantin Belousov from comment #15)
Let me try that tunable today.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
--- Comment #15 from Konstantin Belousov ---
(In reply to Zhenlei Huang from comment #13)
Any exception can be programmed to either cause VM exit or to be reflected
directly
into the VM. For Intel VMX, see vol.3 26.6.3 Exception Bitmap.
B
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
--- Comment #14 from Michael Osipov ---
(In reply to Konstantin Belousov from comment #12)
Well, that's obviously the case since the vm-bhyve.log does not contain any
message of the issue whatsoever. From a user's perspective this isn't he
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
--- Comment #13 from Zhenlei Huang ---
(In reply to Konstantin Belousov from comment #12)
> No, if the guest issues undefined instruction, it must be reflected as the
> corresponding exception (#UD) back to the guest. It is up to the guest
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
--- Comment #12 from Konstantin Belousov ---
(In reply to Zhenlei Huang from comment #11)
No, if the guest issues undefined instruction, it must be reflected as the
corresponding exception (#UD) back to the guest. It is up to the guest cod
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
--- Comment #11 from Zhenlei Huang ---
(In reply to Zhenlei Huang from comment #10)
Emm I must be drunk, but I do not drink ;)
> I'm not familiar with bhyve, but the issue may be related to AMD CPU. It
> may be > `Unable to Reproduce` t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
Zhenlei Huang changed:
What|Removed |Added
Resolution|Unable to Reproduce |---
Status|Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
--- Comment #9 from Michael Osipov ---
Guys,
with all due respect, but I have created this issue. At least have some
courtesy and ask me whether I agree closing this issue.
I would have been totally fine closing it if someone who is knowl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288237
Alexander Ziaee changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203643
--- Comment #22 from NAKAJI Hiroyuki ---
(In reply to ShengYi Hung from comment #20)
The new patch worked for me, too (NetBSD 10.1 and Debian 12). Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
1 - 100 of 1514 matches
Mail list logo
