https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270805
--- Comment #24 from Mark Millard ---
(In reply to Robert Clausecker from comment #22)
FYI:
I have tested one of the latest aarch64 snapshots,
with /boot/loader.conf adjusted, and it worked fine
for booting the Windows Dev Kit 2023 as the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264300
Marko Cupać changed:
What|Removed |Added
CC||marko.cu...@mimar.rs
--- Comment #5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256143
Graham Perrin changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270472
--- Comment #2 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=4b39a12830feaf2ac49b157ed079c04114b1a3ca
commit 4b39a12830feaf2ac49b157ed079c04114b1a3ca
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270472
Mark Johnston changed:
What|Removed |Added
Resolution|--- |FIXED
Assignee|b...@free
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=271038
Bug ID: 271038
Summary: "posixshmcontrol ls" gets an error when another user
restricts some shared memory
Product: Base System
Version: 12.3-RELEASE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269780
--- Comment #6 from Konstantin Belousov ---
https://reviews.freebsd.org/D39773
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271038
--- Comment #1 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=043e24bdb01938c0d5a73a3192e316ce0b96ec1b
commit 043e24bdb01938c0d5a73a3192e316ce0b96ec1b
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270964
Mark Linimon changed:
What|Removed |Added
Keywords||IntelNetworking
Assignee|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270975
--- Comment #2 from nk...@demig.de ---
I would like to repeat: I've found that some thread remained in unkillable
sleep in syscall sync(). For me, that does not look like a performance problem.
And all of the io prcesses do some random sleep
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270975
--- Comment #3 from nk...@demig.de ---
And, may be I've forgot to mention. We first saw the problem in our embedded
environment without heavy io, just a lot of syncing at rtprio. It needed a lot
more time, weeks at least, to hang the system
12 matches
Mail list logo