https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203884
Bug ID: 203884
Summary: bhyve exits with assert when vcpu already in use
Product: Base System
Version: 10.2-STABLE
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203531
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203884
--- Comment #1 from Garrett Cooper,425-314-3911 ---
(In reply to will from comment #0)
Hi will,
The patch should be modified to only exit when vm_activate_cpu returns
error != 0.
Thanks!
-NGie
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203889
Bug ID: 203889
Summary: MacBook UGA issues at login prompt.
Product: Base System
Version: 11.0-CURRENT
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203891
Bug ID: 203891
Summary: Consider supporting linux' sync_file_range()
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203891
Kubilay Kocak changed:
What|Removed |Added
Keywords||feature,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203746
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
Mateusz Guzik changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203707
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203707
eu...@grosbein.net changed:
What|Removed |Added
Attachment #161926|0 |1
is obsolete|
Hi b...@freebsd.org,
christianmedia...@gmail.com added you to the christianmedia175 group.
https://groups.google.com/d/forum/christianmedia175
Message from christianmedia...@gmail.com:
Dear Christian Media Friend,
We show you as receiving our prophecy publication, the Christian Media
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
--- Comment #2 from Rizal Muhammad Nur ---
Created attachment 162257
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162257=edit
Load file which is generated by dummyFileGenerator.py
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203901
Bug ID: 203901
Summary: 'service local_unbound reload' stops name resolution
inside jails (but not on host)
Product: Base System
Version: 10.1-RELEASE
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
--- Comment #7 from Garrett Cooper,425-314-3911 ---
(In reply to Garrett Cooper,425-314-3911 from comment #6)
Answering my own question about include/stdio.h: yes, we did (and I remember
some of the context for issues
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
Bug ID: 203900
Summary: Can not increase above 32K max open files descriptor
per PID
Product: Base System
Version: 10.1-STABLE
Hardware: amd64
OS:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
--- Comment #1 from Rizal Muhammad Nur ---
Created attachment 162256
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162256=edit
Generate many dummy files
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203891
--- Comment #4 from Warner Losh ---
making sync_file_range should be straight forward. fsync
is internally implemented as sync_file_range(0, 0, SYNC)
in the kernel right now, so adding the right glue in the kernel
would
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203891
--- Comment #3 from Warner Losh ---
making sync_file_range should be straight forward. fsync
is internally implemented as sync_file_range(0, 0, SYNC)
in the kernel right now, so adding the right glue in the kernel
would
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203707
--- Comment #8 from Ed Maste ---
> I've attached same patch with -r replaced to -R. Original patch should
> be rolled back before applying this one.
Thank you. I've mentioned the conflicting makefs options on the
Hey FreeBSD,
Join me and over 300 Million other members (over 33 Million from India) on
LinkedIn. You can build important contacts to help grow your career and find
good job opportunities from India and abroad. Start by viewing my full profile.
Vijay Uppn
Technopreneur
Bengaluru Area, India
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203891
cr...@rlwinm.de changed:
What|Removed |Added
CC||cr...@rlwinm.de
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
--- Comment #9 from John Baldwin ---
The relevant patches (I should move these to a git branch) are at
www.freebsd.org/~jhb/patches/stdio_file.patch as well as the
stdio_file_exp*.patch follow up patches from when I was
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202365
John-Mark Gurney changed:
What|Removed |Added
Status|New |Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
--- Comment #10 from John Baldwin ---
The patch for perl sources is at
https://people.freebsd.org/~oshogbo/perl-fdclose.patch All of the perl ports
have to be patched before we can resume doing exp-runs of the source
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
--- Comment #8 from John Baldwin ---
I have a long-lived patch to expand _file inside of FILE from short to int.
However, there is some fallout in other ports (perl uses _file directly :()
that needs to be fixed before
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #3 from bhav...@vmware.com ---
(In reply to Marius Strobl from comment #2)
I tried to search for the history behind why this quirk was introduced for
VMware virtual machines in the first place, as we've never shipped a version
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
Andrey A. Chernov changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203884
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203906
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200397
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200859
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203906
Bug ID: 203906
Summary: ZFS lockup, spa_namespace_lock
Product: Base System
Version: 10.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203900
--- Comment #12 from Rizal Muhammad Nur ---
(In reply to Garrett Cooper,425-314-3911 from comment #7)
Should I try this patch?
www.freebsd.org/~jhb/patches/stdio_file.patch
And may I know how to apply this patch?
36 matches
Mail list logo