https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283123
--- Comment #8 from Michael ---
Just switched to the 14.2 be as you suggested (you were right I needed to
execute freebsd-update again - as the environment was not complete). Also
checked with uname that I was indeed in the 14.2. be.
Then
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283163
Bug ID: 283163
Summary: kill -SIG -1 does not work any more for host - which
leads to inconsistent reboot
Product: Base System
Version: 14.2-RELEASE
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283123
--- Comment #9 from Michael ---
FYI: After rebooting I was back in the 14.1 environment (-t switch from bectl)
which then came up with kernel page errors and auto rebooted.
I then switched to single user (which gave me a shell) and activat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283159
Bug ID: 283159
Summary: crash dump backtraces broken on arm64
Product: Base System
Version: 15.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283116
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=283115
Mark Linimon changed:
What|Removed |Added
Assignee|standa...@freebsd.org |b...@freebsd.org
Component
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283159
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272787
--- Comment #9 from Jason W. Bacon ---
(In reply to ed crowe from comment #8)
Thanks, but unfortunately, those tools only work on macOS, and this is a
FreeBSD-only install. I'll see if I can find the SMC info for this model
elsewhere.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283163
--- Comment #6 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=831531a82e0f1d1d7b97e50c0587639322ed8d2e
commit 831531a82e0f1d1d7b97e50c0587639322ed8d2e
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275764
Daniel Tameling changed:
What|Removed |Added
Attachment #247279|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283090
Nick Briggs changed:
What|Removed |Added
CC||nicholas.h.bri...@gmail.com
--- Comm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281828
--- Comment #6 from Graham Percival ---
@emaste:
I based my patch on the man page for qsort_s (3); seen in
lib/libc/stdlib/qsort.3
or
https://reviews.freebsd.org/D23174
My interpretation of that page is "everything under the #defin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283170
Bug ID: 283170
Summary: jexec(8): add -w parameter to change the working
directory inside the jail
Product: Base System
Version: Unspecified
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268186
--- Comment #63 from amend...@gmail.com ---
Any update on updating Heimdal in the base system?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278124
John Baldwin changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
Status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268186
--- Comment #64 from Cy Schubert ---
(In reply to amendlik from comment #63)
In my estimation the MIT replacement is ~ 80% complete.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283163
--- Comment #1 from v...@fbsd.ru ---
And, looks like (need to prove) that whole patch changed behaviour of sending
signals from host (jid=0) to pid=-1 - it always calls prison_proc_iterate() not
only when jid != 0
which breaks previous contr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283108
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283102
Mark Johnston changed:
What|Removed |Added
Status|New |Open
Assignee|b...@freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283110
--- Comment #2 from John Baldwin ---
It looks like we started installing kernels as 444 instead of 555 in 13.3 and
14.1 due to this commit:
commit a9758e46473babc03bfe06edfec35e0c71fa7780
Author: Konstantin Belousov
Date: Sat Nov 25 15:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283110
John Baldwin changed:
What|Removed |Added
Summary|freebsd-update IDS vs. |freebsd-update IDS vs.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282993
Warner Losh changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283088
Mark Johnston changed:
What|Removed |Added
CC||delp...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161013
Mark Johnston changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283163
--- Comment #4 from Konstantin Belousov ---
Try https://reviews.freebsd.org/D47943
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283093
Warner Losh changed:
What|Removed |Added
Assignee|b...@freebsd.org|i...@freebsd.org
Status|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283091
Warner Losh changed:
What|Removed |Added
CC||i...@freebsd.org
Assignee|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283113
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283130
--- Comment #2 from Ed Maste ---
Issue with drm-kmod is noted in the 14.2 errata (but not release notes,
unfortunately) https://www.freebsd.org/releases/14.2R/errata/:
> drm-kmod packages compiled on FreeBSD 14.1 result in the text console
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283159
--- Comment #2 from John Baldwin ---
Nothing has changed in unwinding for kgdb in a long while, and the only frame
unwinding that is custom in kgdb is for exception frames. Unwinding out of
doadump() is a "normal" frame just like a userspa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283159
John Baldwin changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
Summary
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283091
Warner Losh changed:
What|Removed |Added
Status|New |Closed
Assignee|i...@freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283110
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283090
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112
Mark Linimon changed:
What|Removed |Added
Keywords||vendor
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283043
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283037
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|i...@freebsd.org
C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112
Muhammad Moinur Rahman changed:
What|Removed |Added
CC||b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283043
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #2 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283123
--- Comment #10 from Daniel Tameling ---
It depends on how motivated you are. Since you have a working workaround, you
can just wait until 14.1 hits EOL and once the pkg packages get updated to 14.2
you try drm 6.1 again and file a new bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275764
Ed Maste changed:
What|Removed |Added
CC||d...@freebsd.org,
|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283115
--- Comment #2 from Graham Perrin ---
(In reply to gnath from comment #0)
> from working system
Which version, exactly? For that working system, please:
freebsd-version -kru ; uname -aKU
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282916
Philip Paeps changed:
What|Removed |Added
CC||d...@freebsd.org
Assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282909
Robert Wing changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282909
Robert Wing changed:
What|Removed |Added
Assignee|b...@freebsd.org|r...@freebsd.org
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283016
--- Comment #2 from Dan-Simon Myrland ---
(In reply to Mark Johnston from comment #1)
I get no feedback, the system just reboots at the stage where it's normally
reloading the tty graphics (where you get better tty resolution) and it keeps
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278124
--- Comment #3 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=984add354edef8a6b4983a33f89ff62532a1556b
commit 984add354edef8a6b4983a33f89ff62532a1556b
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283043
--- Comment #4 from John Baldwin ---
Created attachment 255669
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255669&action=edit
geliboot_auth.patch
Better patch that also disables writes
--
You are receiving this mail because
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283163
--- Comment #2 from v...@fbsd.ru ---
Issue triggered is any jail was created since boot, w/o jail looks like proc
iteration falls back to old algorythm and works as expected
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283159
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282930
--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=e7aec3ccf759dcd3fe56ae2bdbec92839c166160
commit e7aec3ccf759dcd3fe56ae2bdbec92839c166160
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283130
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281828
--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=d0a3fd34a05794bc5cbf48709001a78e9f85169a
commit d0a3fd34a05794bc5cbf48709001a78e9f85169a
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281828
--- Comment #5 from Ed Maste ---
The spacing is maybe not completely clear about to what the #define applies,
but perhaps this is consistent with all cases of this.
#include
char *
fgets(char * restrict str, int size, FILE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279261
Mark Johnston changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271791
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|ma...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270404
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|ema...@freebsd.org
Resoluti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282930
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|i...@freebsd.org
Resolution
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278124
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #2 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283163
Eugene Grosbein changed:
What|Removed |Added
CC||eu...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282916
Jose Luis Duran changed:
What|Removed |Added
CC||jldu...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283043
John Baldwin changed:
What|Removed |Added
CC||allanj...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282916
Mark Johnston changed:
What|Removed |Added
CC||i...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283163
--- Comment #5 from v...@fbsd.ru ---
Fix helped:
---
# kill -TERM -1
#
FreeBSD/amd64 (ha) (ttyu0)
login:
---
# shutdown -r now
Shutdown NOW!
shutdown: [pid 22088]
*** FINAL System shutdown message from vova@ha.sunrise ***
System g
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283016
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281828
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #3 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281828
Alexander Ziaee changed:
What|Removed |Added
Status|New |In Progress
Component|b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283170
Jesús Daniel Colmenares Oviedo changed:
What|Removed |Added
Attachment #255678|0 |1
is obsol
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283110
--- Comment #3 from w...@psr.com ---
(In reply to Mark Johnston from comment #1)
Doing a chmod 444 is easy enough. I didn't because I wasn't (previously) 100%
sure doing so was OK, especially on the kernel file itself which something
obvio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112
--- Comment #4 from Yanhui He ---
(In reply to Bjoern A. Zeeb from comment #3)
Thanks Mark and Bjoern!
pycdlib package keeps same in the last 3 years.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283112
--- Comment #3 from Bjoern A. Zeeb ---
(In reply to Mark Johnston from comment #2)
Or not be downloaded to the staging area but only installed into it.
Hmm. I'll look into it.
Likely unrelated to the pycdlib problem tough unless it's the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283110
--- Comment #4 from w...@psr.com ---
(In reply to John Baldwin from comment #2)
> I'm not sure if we want to automate the permission change across these
> versions?
I would think that setting file permissions appropriately for the version be
73 matches
Mail list logo