https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272129
Graham Perrin changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272139
Graham Perrin changed:
What|Removed |Added
Assignee|b...@freebsd.org|grahamper...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272139
Bug ID: 272139
Summary: loader(8) description, and see also, with regard to
kernel modules
Product: Documentation
Version: Latest
Hardware: Any
OS: An
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271989
--- Comment #7 from Markus Wild ---
(In reply to Dan Langille from comment #5)
Check whether you have "ghost" zfs labels on your main drives, besides
the expected ones in the zfs partitions:
zdb -l /dev/ada0
zdb -l /dev/ada1
if yours is t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262180
Graham Perrin changed:
What|Removed |Added
Status|New |Open
Keywords|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272135
--- Comment #2 from Ed Maste ---
On jhb's suggestion I checked with PCIe HP disabled (hw.pci.enable_pcie_hp=0 in
loader.conf) and the NVMe device is detected at boot.
Also suggested checking pciconf -lc pcib7, which reports DPC:
ecap 0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271989
Magnus Kaiser changed:
What|Removed |Added
CC||free...@4xoc.com
--- Comment #6 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272135
Thierry Thomas changed:
What|Removed |Added
CC||thie...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272127
--- Comment #5 from Peter Eriksson ---
(In reply to Konstantin Belousov from comment #4)
A custom kernel with that fix seems to solve the problem!
# umount /compat/linux/dev/fd
# mount /compat/linux/dev/fd
# ./tst -axrd /home/peter86 RUNU
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262969
Ed Maste changed:
What|Removed |Added
See Also|https://bugs.freebsd.org/bu |
|gzilla/show_bug.cgi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271888
Ed Maste changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272135
Ed Maste changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272135
Bug ID: 272135
Summary: hot-swap NVMe drive not consistently detected
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262969
--- Comment #12 from Lucas Holt ---
It appears this is a problem with the WD SN770 in general.
https://github.com/openzfs/zfs/discussions/14793
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271991
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272119
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271607
Ed Maste changed:
What|Removed |Added
Depends on||271047
Referenced Bugs:
https://bugs.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272117
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=272090
Mark Linimon changed:
What|Removed |Added
Keywords||IntelNetworking
Assignee|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272089
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=271989
Dan Langille changed:
What|Removed |Added
CC||d...@freebsd.org
--- Comment #5 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272018
Stefan Eßer changed:
What|Removed |Added
Attachment #242810|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272129
--- Comment #9 from Mina Galić ---
I'm really confused about @imp's comment here
> I don't think this is a good idea
>
> Setting sysctl values multiple times may be unwise.
>
> Most modules should be loaded in the loader, and most conf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272127
--- Comment #4 from Konstantin Belousov ---
Try https://reviews.freebsd.org/D40700
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272018
--- Comment #5 from Stefan Eßer ---
Created attachment 242927
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242927&action=edit
Updated VPD patch
This patch removes a few superfluous tests for allocations that cannot fail and
fo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272117
--- Comment #2 from NL ---
I am experiencing a similar issue with Broadcom BCM57414 on TrueNAS 13. Despite
not having jumbo frame configuration, the NIC with the latest firmware
(225.1.95.0) encounters problems. Interestingly, another card
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272117
NL changed:
What|Removed |Added
CC||noslin...@gmail.com
Attachment #242925|text/x
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272129
--- Comment #8 from d...@rabson.org ---
Hmm - clearly my simplistic solution is not going to work well. I liked Alan
Jude's suggestion in the linked review which adds /etc/sysctl.conf.d for
module-specific values.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271882
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272129
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #7 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272129
--- Comment #6 from d...@rabson.org ---
As Mina already noted, setting kldxref_module_path is a better way of
controlling the search path so I don't think this is a problem. IMO, the
violation of POLA where a user adds a module to kld_list b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272127
Peter Eriksson changed:
What|Removed |Added
Attachment #242920|text/x-csrc |text/plain
mime type|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272127
--- Comment #2 from Peter Eriksson ---
It's not just related to O_DIRECTORY but a more general problem with fdescfs...
root@runur00:/export/build/samba # umount /compat/linux/dev/fd
root@runur00:/export/build/samba # mount /compat/linux/de
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272129
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #5 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272127
--- Comment #1 from Konstantin Belousov ---
PR 255625 / D30131 fixes that. I believe it was not committed waiting on
your feedback.
But even with D30131 applied, the result of your test program is EACCES,
because
you opened fd 3 with O_PA
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272129
--- Comment #4 from Mina Galić ---
(In reply to dfr from comment #2)
please note that the project has been trying to discourage submitting patches
on bugzilla: https://docs.freebsd.org/en/articles/contributing/
GitHub and Phabricator are t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
--- Comment #11 from commit-h...@freebsd.org ---
A commit in branch stable/12 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=bb727917364f7ded1d24f599389288c63b23d862
commit bb727917364f7ded1d24f599389288c63b23d862
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185546
--- Comment #10 from commit-h...@freebsd.org ---
A commit in branch stable/12 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=bb727917364f7ded1d24f599389288c63b23d862
commit bb727917364f7ded1d24f599389288c63b23d862
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272129
--- Comment #3 from d...@rabson.org ---
I don't the use of kern.module_path is a problem - this variable is exported by
the kernel linker itself and cannot be in a loadable module.
--
You are receiving this mail because:
You are the assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272129
--- Comment #2 from d...@rabson.org ---
Created attachment 242919
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=242919&action=edit
Make sysctl require kld
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238408
Tijl Coosemans changed:
What|Removed |Added
Resolution|--- |FIXED
Assignee|b...@fre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272129
Mina Galić changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272129
Bug ID: 272129
Summary: rc.d/kld should run before rc.d/sysctl
Product: Base System
Version: 13.1-RELEASE
Hardware: Any
OS: Any
Status: New
Severity
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271764
--- Comment #2 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=17050a2b5b07160635aaa80b9aa4df4de500b090
commit 17050a2b5b07160635aaa80b9aa4df4de500b090
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272127
Mina Galić changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272126
--- Comment #1 from Mina Galić ---
this seems to be a limitation of the https://man.freebsd.org/setupterm(3)
function.
the code is there,
https://github.com/freebsd/freebsd-src/blob/133b132bc1b612abe591c8f54680c3da8491e194/contrib/nvi/cl/cl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272127
Bug ID: 272127
Summary: fdescfs with linkrdlnk fails openat with O_DIRECTORY
unless "ls -l" done in fdescfs dir first...
Product: Base System
Version: 13.2-RELEASE
Ha
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272126
Mina Galić changed:
What|Removed |Added
CC||free...@igalic.co
Status|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272126
Bug ID: 272126
Summary: vi: Misleading error "No terminal database found" in
case of unsupported terminal type
Product: Base System
Version: 13.2-RELEASE
Hardware: An
49 matches
Mail list logo
