https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262098
Jose Luis Duran changed:
What|Removed |Added
CC||jldu...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282592
Vladimir Kondratyev changed:
What|Removed |Added
Status|New |In Progress
Assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282592
--- Comment #1 from Vladimir Kondratyev ---
Created attachment 255377
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255377&action=edit
hid-signedness.patch
Test this patch
--
You are receiving this mail because:
You are the a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282647
--- Comment #3 from Duane ---
That change seems like a backwards decision. Instead of configuring the
program to not clear the screen when it exits, we lie about whether the
terminal is capable of clearing the screen? If using `less` you
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282901
Bug ID: 282901
Summary: find(1): ls(1) equivalent for "-ls" is wrong
Product: Documentation
Version: Latest
Hardware: Any
OS: Any
Status: New
Severi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282647
--- Comment #2 from Jan Beich ---
(In reply to Duane from comment #1)
ti/te were moved from xterm to xterm-clear due to POLA in base 9190ba057c57.
tmux in termcap does have ti/te but the behavior is controlled by
alternate-screen option (si
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280679
--- Comment #6 from Cullum Smith ---
Thanks for the detailed explanation. Installing terminfo-db indeed resolves the
issue.
I suppose this issue can be closed, since it sounds like termcap is functioning
as designed.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280679
Jan Beich changed:
What|Removed |Added
CC||b...@freebsd.org
--- Comment #5 from J
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282860
--- Comment #41 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=e6ec41fa86d88f80bd663e55455a6844619a9b24
commit e6ec41fa86d88f80bd663e55455a6844619a9b24
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262493
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257732
Mark Johnston changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258496
Mark Johnston changed:
What|Removed |Added
CC||6...@dir.bg
--- Comment #6 from Ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254040
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263411
Mark Johnston changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Sta
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280078
--- Comment #1 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=169e23d41f8ff16244f4fb04924fdc9828325dce
commit 169e23d41f8ff16244f4fb04924fdc9828325dce
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282887
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282877
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|p...@freebsd.org
C
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282891
Bug ID: 282891
Summary: gptboot and loader.efi can't work with geli encrypted
virtio_block devices
Product: Base System
Version: 14.1-STABLE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281443
--- Comment #2 from Ed Maste ---
#1, #3 and #4 do not apply
#2 may apply to 13.3/13.4
#5 needs more information/investigation
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282860
--- Comment #40 from kei...@motavalli.me ---
Created attachment 255361
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255361&action=edit
with the last revision of the patch the system boots
With the last revision of the patch to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282860
--- Comment #39 from Konstantin Belousov ---
Try the updated patch in the review.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282860
--- Comment #38 from kei...@motavalli.me ---
(In reply to Mark Johnston from comment #37)
Hello, the motherboard is running the last bios update (that was the first
thing I updated when having problems some weeks ago once I got hold of this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282860
--- Comment #37 from Mark Johnston ---
(In reply to keivan from comment #36)
Does the Linux dmesg show anything relating to EFI at all?
Are there any BIOS updates available for this motherboard?
--
You are receiving this mail because:
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282860
--- Comment #35 from Mark Johnston ---
I wonder if Linux's efirt time works properly on this system? That is, is
there a rtc-efi clock visible from procfs?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282860
--- Comment #36 from kei...@motavalli.me ---
(In reply to Mark Johnston from comment #35)
Debian 12 (linux 6.1) seems to be using the rtc-cmos driver instead of efi-rtc
ls -l /dev/rtc0
crw--- 1 root root 251, 0 21 nov 13.00 /dev/rtc0
c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282887
Mark Linimon changed:
What|Removed |Added
Keywords||vendor
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282891
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualizat...@freebsd.org
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282832
--- Comment #16 from Pat Maddox ---
Doc update works for me! Thanks
(I don't know if I get to close this PR, or someone else should)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281965
--- Comment #3 from scineram ---
ZFS and Linux supports 1023 bytes, so the new limit should be at least that
much. I don't know about other filesystems in FreeBSD.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282860
--- Comment #34 from kei...@motavalli.me ---
Created attachment 255357
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255357&action=edit
FreeBSD15-CURRENT debug BP pflags output
Attached is the new debug output
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282860
--- Comment #33 from Konstantin Belousov ---
(In reply to keivan from comment #32)
The source code for the faulting instruction is stored somewhere at the BIOS
vendor office. It is EFI RT call into BIOS that causing the #BP exception
durin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282887
Bug ID: 282887
Summary: [13.4]Broadcom mpi3mr driver: DMA allocation fails
Product: Base System
Version: 13.4-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282860
--- Comment #32 from kei...@motavalli.me ---
is there any step I can try to identify the offending line of code for
instruction pointer 0x4e6134ec when successfully booting the system without
efirtc?
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282860
--- Comment #31 from kei...@motavalli.me ---
Created attachment 255354
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255354&action=edit
unrel mutex warnings
The results of testing the D47694 patch are:
-booting with the patch a
34 matches
Mail list logo
