[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279

--- Comment #42 from Peter Eriksson  ---
(In reply to commit-hook from comment #33)

> I've also noted my extreme reservations about making the cr == NULL
> panic just a printf. There's some race that's causing it (I think
> with where we set the shutdown flag racing another thread that's setting it 
> w/o 
> ciss_mtx held). Ideally, someone would chase that to ground who had the 
> hardware and > the time to do so, but I do not.

Perhaps we should make that panic / printf fix selectable via a sysctl knob? I
agree that there is a bug somewhere since with the change to printf() I
sometimes see a never-ending loop with errors instead. However, that takes
longer to "develop" than the panic-reboot so it still makes it a bit more
usable... It typically occurs with bad disks though, so another fix is to
remove the bad disks :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282156] page fault while in kernel mode after 14.0-Release to 14.1-Release upgrade

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282156

Mark Johnston  changed:

   What|Removed |Added

 Status|New |Open
 CC||ma...@freebsd.org,
   ||rmack...@freebsd.org

--- Comment #1 from Mark Johnston  ---
Are you able to get a kernel dump, so that we can pinpoint where the crash is
happening?  If so, there should be some files in /var/crash; core.txt in
particular would be useful to see.

The crash is happening in the NFS code, so some details on your configuration
(relevant rc.conf variables and NFS exports) would also be useful.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 201102] Realtek 892 recognized but no sound?

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201102

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #1 from Christos Margiolis  ---
Is this still an issue in current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282156] page fault while in kernel mode after 14.0-Release to 14.1-Release upgrade

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282156

Bug ID: 282156
   Summary: page fault while in kernel mode after 14.0-Release to
14.1-Release upgrade
   Product: Base System
   Version: 14.1-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: tfag...@brozs.net

Hello,

After a classical upgrade using freebsd-update, my two Freebsd nodes begins to
get unstable. (unwanted reboot)
I've downgrade one of them and this one is now ok in terms of stability.
For the one which is still in 14.1, i'm able to reproduce the reboot by trying
to copy small files over nfs.

Here is the output :

Hardware
CPU: AMD GX-412TC SOC
RAM : 4G

Trace
#
Code:
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address   = 0xd0
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x80e1cd1b
stack pointer   = 0x28:0xfe0084b92a90
frame pointer   = 0x28:0xfe0084b92bc0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 1203 (nfscbd: master)
rdi:  rsi: f80045961828 rdx: 0001
rcx: fe0084b92b00  r8: 0090  r9: 31302d34
rax:  rbx: f80129262000 rbp: fe0084b92bc0
r10:  r11: fe0008b28b20 r12: f80045961800
r13: f80045961880 r14: f80006036000 r15: f80006036100
trap number = 12
panic: page fault
cpuid = 2
time = 1720334146
KDB: stack backtrace:
#0 0x80b7fbfd at kdb_backtrace+0x5d
#1 0x80b32961 at vpanic+0x131
#2 0x80b32823 at panic+0x43
#3 0x80fff91b at trap_fatal+0x40b
#4 0x80fff966 at trap_pfault+0x46
#5 0x80fd6a48 at calltrap+0x8
#6 0x80e1c558 at svc_run+0x1a8
#7 0x809f3933 at nfscbd_nfsd+0x113
#8 0x80a1e8fd at nfssvc_nfscl+0x27d
#9 0x80d83158 at sys_nfssvc+0x98
#10 0x810001c0 at amd64_syscall+0x100
#11 0x80fd735b at fast_syscall_common+0xf8
Uptime: 9h22m40s
Dumping 947 out of 4036 MB:..2%
Dump aborted

#
I can collect more information if needed.

Thanks for your help

Best Regards

Thomas

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 201102] Realtek 892 recognized but no sound?

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201102

Christos Margiolis  changed:

   What|Removed |Added

 Status|New |In Progress

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 201102] Realtek 892 recognized but no sound?

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201102

Christos Margiolis  changed:

   What|Removed |Added

 Status|In Progress |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 236495] sysctl won't set dev.pcm.3.rec.vchanformat=s16le:1.0

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236495

--- Comment #2 from Per Gunnarsson  ---
Created attachment 254311
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254311&action=edit
dmesg

dmesg from last boot

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281541] rpcinfo: format of argument to -a flag is undocumented

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281541

Jim B.  changed:

   What|Removed |Added

 CC||j...@jimby.name

--- Comment #2 from Jim B.  ---
Created attachment 254317
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254317&action=edit
Proposed change incorporating text from RFC 5665

I took a stab at incorporating the text from RFC5665 into the man page for
rpcinfo(8).  Check the attachment.

If acceptable, I'll generate a diff and push to Phabricator.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282001] Inappropriate "BOOT LOADER IS TOO OLD" / missing initialization of bootprog_rev in lutils.c

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282001

--- Comment #4 from Warner Losh  ---
a50d73d5782a3 does not cleanly apply to the target branches, so I'd punted
until now...

Now that I look at it, it's easy enough to fix, which I'm testing now. The
merge conflict is git being too conservative around context, which normally is
fine, but made me thing it was going to be a hassle to resolve. Turns out no,
and I'll push once I confirm.

releng/13.4 shipped like this, and that's too bad. The warning is harmless
there,
though admittedly scary. We should add it as an erratum to the release notes,
if it's not too late.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 258049] vm_reserv_depopulate panic.

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258049

--- Comment #13 from Mark Johnston  ---
Is this PR still relevant?  The riscv pmap has gotten a number of bug fixes
which may have addressed this particular panic.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 258049] vm_reserv_depopulate panic.

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258049

--- Comment #14 from dgilb...@eicat.ca ---
I am still doing poudriere on a regular basis on RISC-V hardware.  I also
regularly recompile -CURRENT to update.  Neither has caused this recently, but
I cannot truly verify that it's fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282168] vtnet(4): panic in if_attach_internal() when kldloading

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168

Bug ID: 282168
   Summary: vtnet(4): panic in if_attach_internal() when
kldloading
   Product: Base System
   Version: 15.0-CURRENT
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: lexi.free...@le-fay.org

bhyve guest: FreeBSD 15.0-CURRENT #0 lf/main-n269061-b4479cf2b3b9: Wed Sep 18
20:43:02 BST 2024
srcma...@daphne.eden.le-fay.org:/src/obj/src/freebsd/lf/main/amd64.amd64/sys/LFV6

bhyve host: FreeBSD 15.0-CURRENT #43 lf/main-n269060-ffd494371643: Tue Sep 17
05:59:59 BST 2024
srcma...@daphne.eden.le-fay.org:/src/obj/src/freebsd/lf/main/amd64.amd64/sys/LF

'kldloat virtio_pci' causes a kernel panic when vtnet is loaded.

stack trace (i have a vmcore if needed):

root@lily:~ # kldload virtio_pci
virtio_pci0:  port 0x2000-0x203f mem
0xc000-0xc0001fff irq 18 at device 5.0 on pci0
root@lily:~ # vtnet0:  on virtio_pci0


Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address   = 0x28
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x8051deb8
stack pointer   = 0x28:0xfe004b379810
frame pointer   = 0x28:0xfe004b379850
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 701 (devctl)
rdi: f80001021300 rsi: f80001021300 rdx: 0001
rcx: 0001  r8: 0010  r9: fe0001e0a040
rax:  rbx: f80001f02000 rbp: fe004b379850
r10: f800011b9800 r11: 9e99ff93939e r12: f8000186a800
r13: f800018c0b30 r14: 8070e492 r15: 
trap number = 12
panic: page fault
cpuid = 1
time = 1729195870
KDB: stack backtrace:
#0 0x8045ed4d at kdb_backtrace+0x5d
#1 0x80414bdf at vpanic+0x13f
#2 0x80414a93 at panic+0x43
#3 0x8069d39b at trap_fatal+0x40b
#4 0x8069d3e6 at trap_pfault+0x46
#5 0x806747d8 at calltrap+0x8
#6 0x8051cd8e at if_attach_internal+0x4e
#7 0x80527f6c at ether_ifattach+0x2c
#8 0x8181d6d1 at vtnet_setup_interface+0x391
#9 0x8181cb53 at vtnet_attach+0x1a63
#10 0x8044e96c at device_attach+0x3ac
#11 0x81812497 at vtpci_legacy_probe_and_attach_child+0x77
#12 0x8044c029 at devclass_driver_added+0x29
#13 0x8045453b at device_do_deferred_actions+0x3b
#14 0x80453e3f at devctl2_ioctl+0x20f
#15 0x803811ab at devfs_ioctl+0xcb
#16 0x804fb30e at vn_ioctl+0xce
#17 0x8038180e at devfs_ioctl_f+0x1e
Uptime: 14s
Dumping 113 out of 1002 MB:..15%..29%..43%..57%..71%..85%..99%
Dump complete
Automatic reboot in 15 seconds - press a key on the console to abort

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282112] release: latest GCE images do not work in Cirrus CI

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282112

Alan Somers  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|New |Closed

--- Comment #1 from Alan Somers  ---
Fixed in the freebsd-15-0-current-amd64-ufs-20241017 image.

The problem was the libmd.so version bump.  After it got bumped the 20241003
and 20241010 images were broken because they installed old binary packages that
required the libmd.so.6 library, which was not present.  Then after the package
building cluster built new versions, older images containing libmd.so.6 would
work initially but they were (and still are) unable to install new any
packages.  The newest image finally contains both the libmd.so.7 library and
the packages that expect it.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282168] vtnet(4): panic in if_attach_internal() when kldloading

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168

--- Comment #1 from Lexi Winter  ---
forgot to mention, this works fine if virtio_pci.ko and if_vtnet.ko are loaded
prior to boot in loader.conf.  it's only kldload that triggers the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282001] Inappropriate "BOOT LOADER IS TOO OLD" / missing initialization of bootprog_rev in lutils.c

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282001

Mark Johnston  changed:

   What|Removed |Added

 Status|Open|In Progress

--- Comment #6 from Mark Johnston  ---
(In reply to Warner Losh from comment #4)
Can the problem be fixed without updating boot media?  That is, is it just a
matter of updating /boot/loader_lua?  If so, we can issue an EN with a binary
patch to fix the problem for 13.4 users.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 236495] sysctl won't set dev.pcm.3.rec.vchanformat=s16le:1.0

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236495

Per Gunnarsson  changed:

   What|Removed |Added

 CC||p...@kaffe.mustafejen.se

--- Comment #3 from Per Gunnarsson  ---
Created attachment 254312
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254312&action=edit
sysctls

pcm sysctls

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 236495] sysctl won't set dev.pcm.3.rec.vchanformat=s16le:1.0

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236495

--- Comment #4 from Per Gunnarsson  ---
I just tried with
FreeBSD konjak 14.1-RELEASE FreeBSD 14.1-RELEASE
releng/14.1-n267679-10e31f0946d8 GENERIC amd64

and now (after turning off pulseaudio)

I can set the value, turn on pulseaudio again and adjust
the recording volume with Pulseaudio Volume Control :-)

Thanks a lot!

I used to have to remap the USB microphone to a mono source in pulseaudio

Now I tried adding the sysctl in /etc/sysctl.conf, rebooted
and after this I got the right volume at 100% (0dB) in pulseaudio.

Thanks a lot whoever fixed this :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 236495] sysctl won't set dev.pcm.3.rec.vchanformat=s16le:1.0

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236495

Christos Margiolis  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |FIXED

--- Comment #5 from Christos Margiolis  ---
Nice. :)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282168] vtnet(4): panic in if_attach_internal() when kldloading

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168

Mark Johnston  changed:

   What|Removed |Added

 Status|New |Open
 CC||ma...@freebsd.org

--- Comment #2 from Mark Johnston  ---
What is in your kernel config?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281541] rpcinfo: format of argument to -a flag is undocumented

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281541

--- Comment #3 from Garrett Wollman  ---
Comment on attachment 254317
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254317
Proposed change incorporating text from RFC 5665

Well, that at least makes it clear what the weird format is. I suspect a
.Bd/.Ed block should be used instead of quotation marks here to clearly call
out the quotation, as it's longer than a single sentence. Similarly .Rs/Re with
the appropriate macros for the source citation. The bit about `-T` should be
moved to the second paragraph.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 258049] vm_reserv_depopulate panic.

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258049

Mark Johnston  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Overcome By Events

--- Comment #15 from Mark Johnston  ---
If the problem isn't reproduced by poudriere runs, then I think it's reasonable
to assume that the underlying problem was fixed by one of the myriad riscv pmap
changes that have landed since this PR was submitted.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281541] rpcinfo: format of argument to -a flag is undocumented

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281541

--- Comment #4 from Graham Percival  ---
Thanks for your interest!

At first glance, it looks as though you included more than a whole paragraph
verbatim from RFC 5665.  Is that common practice in FreeBSD?

RFC 5665 states that code components are under the Simplified BSD License
(which is 2-clause); however, the the latest legal provisions [1] say that the
previous version erroneously referred to "simplified BSD license" instead of
"revised BSD license" (which is 3-clause).
[1] https://trustee.ietf.org/documents/trust-legal-provisions/tlp-5/

Also, those are for "code components".  I haven't yet found a definitive
statement about the copyright and licensing for text itself; given that they
carefully define "code components", I suspect that the text is not under so
permissive a license.

...

Also, I don't think this needs such a verbose answer.  My guess is that 2 or 3
sentences, along with a reminder that it's defined in RFC 5665 (with a link in
the SEE ALSO section), would be sufficient.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282168] vtnet(4): panic in if_attach_internal() when kldloading

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168

--- Comment #4 from Lexi Winter  ---
Created attachment 254319
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254319&action=edit
kernel config

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282168] vtnet(4): panic in if_attach_internal() when kldloading

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168

--- Comment #3 from Lexi Winter  ---
Created attachment 254318
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254318&action=edit
kernel config

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282168] vtnet(4): panic in if_attach_internal() when kldloading

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168

--- Comment #5 from Lexi Winter  ---
kernel config attached, note it's two files since "LFV6" includes "LF".  "LFV6"
is the running kernel on this system.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282001] Inappropriate "BOOT LOADER IS TOO OLD" / missing initialization of bootprog_rev in lutils.c

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282001

--- Comment #5 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=dac5a2024bc8bed379d3db861580056d0c670fdc

commit dac5a2024bc8bed379d3db861580056d0c670fdc
Author: Stephen J. Kiernan 
AuthorDate: 2023-04-17 23:27:54 +
Commit: Warner Losh 
CommitDate: 2024-10-17 19:08:21 +

loader: Change version calculation to be more consistent.

Use 1000 * major + minor when calculating the version number that
gets set in the Ficl environment or lua loader property. This allows
for more room if the minor number needs to go above 9.

Add loader.version property to lua loader.

PR: 282001
Reviewed by:imp
Obtained from:  Juniper Networks, Inc.
Differential Revision: https://reviews.freebsd.org/D39631

(cherry picked from commit a50d73d5782a351ad83e8d1f84d11720a12e70d3)

 stand/common/bootstrap.h| 1 +
 stand/common/interp_forth.c | 1 -
 stand/common/newvers.sh | 2 +-
 stand/liblua/lutils.c   | 2 ++
 4 files changed, 4 insertions(+), 2 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282168] vtnet(4): panic in if_attach_internal() when kldloading

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org
   Keywords||crash

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282001] Inappropriate "BOOT LOADER IS TOO OLD" / missing initialization of bootprog_rev in lutils.c

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282001

Mark Linimon  changed:

   What|Removed |Added

  Flags||needs_errata+

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281541] rpcinfo: format of argument to -a flag is undocumented

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281541

--- Comment #5 from Jim B.  ---
Created attachment 254321
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254321&action=edit
Revised description of address format (reply to comments 3 and 4)

Update to the address format in response to comments 3 and 4.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282169] zfs rename deadlock with mountd, df & fstat (and possibly others)

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282169

Bug ID: 282169
   Summary: zfs rename deadlock with mountd, df & fstat (and
possibly others)
   Product: Base System
   Version: 13.4-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: p...@lysator.liu.se

Created attachment 254323
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254323&action=edit
Output from "procstat -kk -a" at the time of the deadlock

Ran into a deadlock involving doing "zfs rename" on a large number of
filesystems on one of our production servers a couple of days ago. 

I was renaming them from DATA/{staff,students}/ to
DATA/archive/{staff,students}/.

While running that script the first 167 (out of about 2) filesystems worked
fine, and then it deadlocked - mountd stopped servicing new requests, a "df -it
zfs" never finished and same with an "fuser" command.

(I run another script from cron every minute that logs how the system looks by
saving the output from "df -it zfs", "fuser", "procstat -kk -a" and a bunch of
other commands, that script also stopped working at the time of the deadlock).


Looking at the output from "procstat -kk -a" (included) it seems the hanging
processes were blocked with some ZFS locks. 

I found an old bug report from around 2016 (209158) where something similar is
discussed, but that was with the old FreeBSD-ZFS code.

I eventually had to hard-reset the server since it never recovered (atleast not
in the 5 hours I waited).

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282001] Inappropriate "BOOT LOADER IS TOO OLD" / missing initialization of bootprog_rev in lutils.c

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282001

Mark Linimon  changed:

   What|Removed |Added

  Flags|needs_errata+   |

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281541] rpcinfo: format of argument to -a flag is undocumented

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281541

--- Comment #7 from Graham Percival  ---
Thanks!

SEE ALSO looks good.

For the -a part, I'd be tempted to leave the first paragraph unchanged -- that
is, keep the mention of -T in there.  In the proposed version, the -T is way at
the bottom and thus easier to overlook.

I think we can omit the "assuming big-endian ordering" -- as per comment 1, the
implementation of rpcinfo in FreeBSD already assumes big-endian.

Also, I'd be tempted to remove the mention of the hex address.  I think that
everybody is familiar with the form 192.168.1.125.

As a more general note, I think this is ready for Phabricator.  (That said, I'm
not a FreeBSD committer or maintainer, so take my opinions with a grain of
salt!)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281541] rpcinfo: format of argument to -a flag is undocumented

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281541

--- Comment #6 from Jim B.  ---
Created attachment 254322
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254322&action=edit
Update to SEE ALSO section to reference RFC 5665.

Update to SEE ALSO to include reference to RFC 5665.  My mandoc/groff is a bit
rusty so please let me know if this is how it should look.

Thanks,
Jim B.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282001] Inappropriate "BOOT LOADER IS TOO OLD" / missing initialization of bootprog_rev in lutils.c

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282001

--- Comment #7 from Warner Losh  ---
For bios, just /boot/loader and loader_lua. For UEFI we have to uodate the ESP.
I'd seriously not do an EN and just issue an errata. An EN would cause more
problems than it would fix.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 98496] [sound] [snd_ich] some functions don't work in my sound kernel module

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=98496

Christos Margiolis  changed:

   What|Removed |Added

 Status|Open|Closed
 CC||chris...@freebsd.org
 Resolution|--- |Feedback Timeout

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 107516] [sound] [snd_emu10k1] - skips, clicks and lag after a day of heavy usage

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=107516

Christos Margiolis  changed:

   What|Removed |Added

 Status|Open|Closed
 CC||chris...@freebsd.org
 Resolution|--- |Feedback Timeout

--- Comment #4 from Christos Margiolis  ---
Thanks for taking the time to submit this bug for the issue you encountered,
and we apologize that it was not addressed in a timely fashion. The FreeBSD
sound subsystem has had a large number of bug fixes and improvements over the
last year or two, and this issue may be fixed. In the absence of feedback
confirming this is still a problem on contemporary FreeBSD versions we are
closing this issue. Please open a new bug if this issue is reproducible on a
supported FreeBSD release.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 100859] [sound] [snd_ich] snd_ich broken on GIGABYTE 915 system

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=100859

Christos Margiolis  changed:

   What|Removed |Added

 Resolution|--- |Feedback Timeout
 Status|Open|Closed
 CC||chris...@freebsd.org

--- Comment #3 from Christos Margiolis  ---
Thanks for taking the time to submit this bug for the issue you encountered,
and we apologize that it was not addressed in a timely fashion. The FreeBSD
sound subsystem has had a large number of bug fixes and improvements over the
last year or two, and this issue may be fixed. In the absence of feedback
confirming this is still a problem on contemporary FreeBSD versions we are
closing this issue. Please open a new bug if this issue is reproducible on a
supported FreeBSD release.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 132511] [sound] [snd_hda] Probing ALC888 codec on ASRock K10N78-1394 fails

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=132511

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #7 from Christos Margiolis  ---
Is this bug still reproducible with current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 87782] [sound] snd_t4dwave and pcm0:record:0: record interrupt timeout, channel dead

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=87782

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #6 from Christos Margiolis  ---
(In reply to gildororonar from comment #4)
Is this still an issue in current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 114760] [sound] [snd_cmi] snd_cmi driver causing sporadic system hangs

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=114760

Christos Margiolis  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Feedback Timeout
 CC||chris...@freebsd.org

--- Comment #4 from Christos Margiolis  ---
Thanks for taking the time to submit this bug for the issue you encountered,
and we apologize that it was not addressed in a timely fashion. The FreeBSD
sound subsystem has had a large number of bug fixes and improvements over the
last year or two, and this issue may be fixed. In the absence of feedback
confirming this is still a problem on contemporary FreeBSD versions we are
closing this issue. Please open a new bug if this issue is reproducible on a
supported FreeBSD release.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 171937] [pcm] Notebook Toshiba Satellite C850-B1K and problem with sound

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171937

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #4 from Christos Margiolis  ---
Is this issue still reproducible with current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 175306] [snd_hda] snd_hda does not produce 7.1 sound on ALC892 chip

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=175306

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #5 from Christos Margiolis  ---
Is this issue still reproducible with current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 174828] [sound] [snd_emu10kx]: "Creative SB PCI512 [CT4790]" is not working at FreeBSD-9.1

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=174828

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #3 from Christos Margiolis  ---
Is this issue still reproducible with current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 182365] [ppc] Sound Blaster (ISA) support is broken

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182365

Christos Margiolis  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 CC||chris...@freebsd.org
 Status|Open|Closed

--- Comment #3 from Christos Margiolis  ---
ISA sound driver support is retired in current versions of FreeBSD.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 201102] Realtek 892 recognized but no sound?

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201102

Christos Margiolis  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Feedback Timeout

--- Comment #2 from Christos Margiolis  ---
Thanks for taking the time to submit this bug for the issue you encountered,
and we apologize that it was not addressed in a timely fashion. The FreeBSD
sound subsystem has had a large number of bug fixes and improvements over the
last year or two, and this issue may be fixed. In the absence of feedback
confirming this is still a problem on contemporary FreeBSD versions we are
closing this issue. Please open a new bug if this issue is reproducible on a
supported FreeBSD release.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 192057] Sound doesn't work, fan on high, Wi-Fi Broadcom BCM43224 doesn't work

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192057

Christos Margiolis  changed:

   What|Removed |Added

 Status|Open|Closed
 CC||chris...@freebsd.org
 Resolution|--- |Feedback Timeout

--- Comment #3 from Christos Margiolis  ---
Thanks for taking the time to submit this bug for the issue you encountered,
and we apologize that it was not addressed in a timely fashion. The FreeBSD
sound subsystem has had a large number of bug fixes and improvements over the
last year or two, and this issue may be fixed. In the absence of feedback
confirming this is still a problem on contemporary FreeBSD versions we are
closing this issue. Please open a new bug if this issue is reproducible on a
supported FreeBSD release.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281638] vi editor ( command -go to the previous sentence- stops at period + 1 space when shouldn't

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281638

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org

--- Comment #1 from Mark Johnston  ---
Sorry for the delay in following up.  Our vi implementation comes from
https://github.com/lichray/nvi2, so issues against it should be reported there.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 231027] [META] FreeBSD-Foundation sponsored issues for FreeBSD-CURRENT

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027
Bug 231027 depends on bug 201052, which changed state.

Bug 201052 Summary: [sctp] capsicum: propagate rights on sctp_peeloff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201052

   What|Removed |Added

 Status|In Progress |Closed
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282156] page fault while in kernel mode after 14.0-Release to 14.1-Release upgrade

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282156

Mark Linimon  changed:

   What|Removed |Added

   Keywords||crash, regression

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 129604] [sound] Sound stops with error: pcm0:virtual:dsp0.vp0: play interrupt timeout, channel dead

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=129604

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #9 from Christos Margiolis  ---
Is this bug reproducible with current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 132848] [sound] [snd_emu10kx] driver problem with card init, snd_emu10k1 inits card correctly

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=132848

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #10 from Christos Margiolis  ---
Is this issue still reproducible with current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 140591] [PATCH][sound] No sound output on lineout/headphone jacks using AD1980 AC'97 codec chip (Fujitsu C610)

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140591

Christos Margiolis  changed:

   What|Removed |Added

 Status|Open|Closed
 CC||chris...@freebsd.org
 Resolution|--- |Feedback Timeout

--- Comment #3 from Christos Margiolis  ---
Thanks for taking the time to submit this bug for the issue you encountered,
and we apologize that it was not addressed in a timely fashion. The FreeBSD
sound subsystem has had a large number of bug fixes and improvements over the
last year or two, and this issue may be fixed. In the absence of feedback
confirming this is still a problem on contemporary FreeBSD versions we are
closing this issue. Please open a new bug if this issue is reproducible on a
supported FreeBSD release.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 143505] [pcm] FreeBSD 8.0-RELEASE (x64) won't make sound card work (Intel ICH5 (82801EB) [regression]

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=143505

Christos Margiolis  changed:

   What|Removed |Added

 Resolution|--- |Feedback Timeout
 CC||chris...@freebsd.org
 Status|Open|Closed

--- Comment #4 from Christos Margiolis  ---
Thanks for taking the time to submit this bug for the issue you encountered,
and we apologize that it was not addressed in a timely fashion. The FreeBSD
sound subsystem has had a large number of bug fixes and improvements over the
last year or two, and this issue may be fixed. In the absence of feedback
confirming this is still a problem on contemporary FreeBSD versions we are
closing this issue. Please open a new bug if this issue is reproducible on a
supported FreeBSD release.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 144659] [pcm] The distortion of the sound playback of music at high volume levels.

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144659

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #7 from Christos Margiolis  ---
(In reply to Alexey from comment #3)
Is this issue still reproducible with current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 162181] [snd_emu10k1] [patch] The kernel sound driver module snd_emu10k1.ko hangs when loaded.

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162181

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #4 from Christos Margiolis  ---
Is this issue still reproducible with current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 164220] sound preferences does not allow continuous adjustment of mic level

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164220

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org
 Status|Open|Closed
 Resolution|--- |Feedback Timeout

--- Comment #3 from Christos Margiolis  ---
Thanks for taking the time to submit this bug for the issue you encountered,
and we apologize that it was not addressed in a timely fashion. The FreeBSD
sound subsystem has had a large number of bug fixes and improvements over the
last year or two, and this issue may be fixed. In the absence of feedback
confirming this is still a problem on contemporary FreeBSD versions we are
closing this issue. Please open a new bug if this issue is reproducible on a
supported FreeBSD release.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 171082] Nvidia GeForce GTX 560 no HDMI Sound

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171082

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #5 from Christos Margiolis  ---
Is this issue still reproducible with current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 120857] [sound] [snd_emu10k1] snd_emu10k1 driver issues a warning on unload

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=120857

Christos Margiolis  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Feedback Timeout
 CC||chris...@freebsd.org

--- Comment #3 from Christos Margiolis  ---
Thanks for taking the time to submit this bug for the issue you encountered,
and we apologize that it was not addressed in a timely fashion. The FreeBSD
sound subsystem has had a large number of bug fixes and improvements over the
last year or two, and this issue may be fixed. In the absence of feedback
confirming this is still a problem on contemporary FreeBSD versions we are
closing this issue. Please open a new bug if this issue is reproducible on a
supported FreeBSD release.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 72995] [sound] Intel ICH2 (82801BA) - sound nearly inaudible

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=72995

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org
 Status|Open|Closed
 Resolution|--- |Unable to Reproduce

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 236495] sysctl won't set dev.pcm.3.rec.vchanformat=s16le:1.0

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236495

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org
 Status|New |Open

--- Comment #1 from Christos Margiolis  ---
Is this issue still reproducible with current versions of FreeBSD? And if yes,
can you show exactly the steps to reproduce it, as well as the setup you have?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 128870] [pccbb] Interrupt Storm when plugging in PCMCIA Card (HP NC8000 Notebook)

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=128870

Christos Margiolis  changed:

   What|Removed |Added

 CC||chris...@freebsd.org

--- Comment #6 from Christos Margiolis  ---
Is this issue still reproducible with current versions of FreeBSD?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 149943] [pcm]: CS4236 audio problem

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=149943

Christos Margiolis  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Overcome By Events
 CC||chris...@freebsd.org

--- Comment #3 from Christos Margiolis  ---
ISA drivers are no longer supported.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 120406] [devd] [patch] Handle newly attached pcm devices (eg. via uaudio)

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=120406

Christos Margiolis  changed:

   What|Removed |Added

 Resolution|--- |Not Accepted
 CC||chris...@freebsd.org
 Status|Open|Closed

--- Comment #7 from Christos Margiolis  ---
(In reply to patfbsd from comment #4)
I agree with this. I think it's better to close this as there is no point in
integrating this behavior in the base system.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282156] page fault while in kernel mode after 14.0-Release to 14.1-Release upgrade

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282156

--- Comment #2 from Rick Macklem  ---
(In reply to Mark Johnston from comment #1)
And the output of "nfsstat -m" could be useful.
The crash appears to be in the client side when
a server->client callback occurs.

Do you have delegations enabled on your NFS server?
(vfs.nfsd.issue_delegations set non-zero on the
server, if it is a FreeBSD one.)

To avoid the crashes, you could try running without
the nfscbd running. (Just change the line in your
/etc/rc.conf.)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282057] newsyslog(8): add option to pass flags by default or at least those which make sense

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282057

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org
 Status|New |Open
   Keywords||feature

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282064] 15-current libpfctl.o fails to compile and stops buildworld

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282064

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org
 Resolution|--- |Not Enough Information
 Status|New |Closed

--- Comment #3 from Mark Johnston  ---
If the issue persists with a checkout of "main", please:
- show the revision you're building
- report the exact command you used to build world
- attach a log of the build output

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282001] Inappropriate "BOOT LOADER IS TOO OLD" / missing initialization of bootprog_rev in lutils.c

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282001

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org,
   ||ste...@freebsd.org
 Status|New |Open

--- Comment #1 from Mark Johnston  ---
It looks like commit a50d73d5782a3 was merged to stable/14 but not 13.  There
is a minor conflict, but I think it applies generally.

Steve, Warner, can we merge this?

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 281921] 13.4R - erroneous boot loader warning ?

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281921

Mark Johnston  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|New |Closed
 CC||ma...@freebsd.org

--- Comment #1 from Mark Johnston  ---
I think this is a duplicate of 282001, please re-open if I'm incorrect.

*** This bug has been marked as a duplicate of bug 282001 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282001] Inappropriate "BOOT LOADER IS TOO OLD" / missing initialization of bootprog_rev in lutils.c

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282001

Mark Johnston  changed:

   What|Removed |Added

 CC||di...@webweaving.org

--- Comment #2 from Mark Johnston  ---
*** Bug 281921 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282001] Inappropriate "BOOT LOADER IS TOO OLD" / missing initialization of bootprog_rev in lutils.c

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282001

--- Comment #3 from di...@webweaving.org ---
In the meantime - may be good to mention this in the errata of 13.X

Dw.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 282156] page fault while in kernel mode after 14.0-Release to 14.1-Release upgrade

2024-10-17 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282156

--- Comment #3 from tfag...@brozs.net ---
(In reply to Rick Macklem from comment #2)



More input
The node where the crash occur is a NFS client.
NFS Server rely on TruenasScale (Debian) release Dragonfish-24.04.1.1

root@www1:~ # cat /etc/rc.conf | grep nfs
nfs_client_enable="YES"
nfsuserd_enable="YES"
nfscbd_enable="YES"

root@www1:~ # nfsstat -m (on a working node in 14.0-RELEASE)
nas-gel64-01:/mnt/big/nfs0 on /net/nas-gel64-01/mnt/big/nfs0
nfsv4,minorversion=2,tcp,resvport,nconnect=1,hard,intr,cto,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=8388608,timeout=120,retrans=2147483647
nas-gel64-01:/mnt/vol1/nfs1 on /net/nas-gel64-01/mnt/vol1/nfs1
nfsv4,minorversion=2,tcp,resvport,nconnect=1,hard,intr,cto,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=8388608,timeout=120,retrans=2147483647


For now I've downgraded the non working node in 14.0-RELEASE, but I can upgrade
again.

-- 
You are receiving this mail because:
You are the assignee for the bug.