[Bug 284621] panic during pkg upgrade

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284621

Mark Millard  changed:

   What|Removed |Added

 CC||marklmi26-f...@yahoo.com

--- Comment #1 from Mark Millard  ---
(In reply to Marek Zarychta from comment #0)

The gdb backtrace has line numbers in source files.

Was this /boot/kernel-NODEBUG/ as built and installed
via PkgBase? That would mean that the files and line
numbers are tied to FreeBSD-src-sys and FreeBSD-src
packages. The 2 need not be based on the exact same
commit for base_latest , for example.

For PkgBase, if one does not have an unmodified copy
of the /usr/src/ tree at the point in question, then
identification of the exact source involved is
problematical.

The PkgBase builds/installs of kernel-NODEBUG or the
like do provide files for /usr/lib/debug/ that provide
some information.


Was it instead based on personal build based on
GENERIC-NODEBUG and some git fetch ? That could
mean that 448f54a3bfe6 is accurate for everything.

(I'm only aware of PkgBase and personal builds
providing GENERIC-NODEBUG builds of main to install.)

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


[Bug 284621] panic during pkg upgrade

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284621

Mark Linimon  changed:

   What|Removed |Added

   Keywords||crash
 CC||p...@freebsd.org

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


[Bug 284616] nfsd thread count auto-tune do not respect MAXNFSDCNT

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284616

Mark Linimon  changed:

   What|Removed |Added

   Keywords||patch
   Assignee|b...@freebsd.org|f...@freebsd.org

--- Comment #1 from Mark Linimon  ---
^Triage: note that there is an inline patch.  (fwiw, we prefer patches to be
attachments.)

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


[Bug 284606] Kernel Panic on wireguard VPN router with a Mikrotik peer

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284606

Mark Linimon  changed:

   What|Removed |Added

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

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


[Bug 109201] callbootd: create a manual page

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=109201

Felix Johnson  changed:

   What|Removed |Added

 CC||felix.the@gmail.com

--- Comment #3 from Felix Johnson  ---
I created a new manual page, callbootd.8.
It needs review.

https://reviews.freebsd.org/D48872

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


[Bug 284621] panic during pkg upgrade

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284621

--- Comment #2 from Marek Zarychta  ---
(In reply to Mark Millard from comment #1)
It wasn't kernel from pkgbase, it was my personal built based on sources
checked out on the evening (19:00 - 20:00 UTC) of Sun Dec 15 2024 having only
one additional, experimental commit[1] from bug 245103, and I would rather not
blame this patch (IPv6 SLAAC temporary addresses/privacy extensions by F. Gont)
for the panic. I have been testing it for almost 1 year without issues.

1. https://bz-attachments.freebsd.org/attachment.cgi?id=252676

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


[Bug 284621] panic during pkg upgrade

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284621

--- Comment #3 from Mark Millard  ---
(In reply to Marek Zarychta from comment #2)

The following from the gdb backtrace indicates it was trying
to do activity in support of ZFS's ARC functionality when it
failed:

#23 arc_reap_cb (arg=, zthr=) at
/usr/src/sys/contrib/openzfs/module/zfs/arc.c:4790
#24 0x8276baed in zthr_create_timer (zthr_name=0xf800019f1960
"\213\334~\202\377\377\377\377", checkfunc=0xf800019f1900, 
func=, arg=0x197fd, max_sleep=6601913001192380413,
pri=-2048) at /usr/src/sys/contrib/openzfs/module/zfs/zthr.c:305

Nothing looks like an obvious tie to IPv6 activity.

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


[Bug 284606] Kernel Panic on wireguard VPN router with a Mikrotik peer

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284606

--- Comment #1 from Wencey Wang  ---
A dump of /var/crash can be found at
https://webresources.dreamry.org/dump284606.tar.gz

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


[Bug 284606] Kernel Panic on wireguard VPN router with a Mikrotik peer

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284606

Bug ID: 284606
   Summary: Kernel Panic on wireguard VPN router with a Mikrotik
peer
   Product: Base System
   Version: 14.2-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: wen...@apernet.io

A router running multiple wireguard tunnels running
14.2-RELEASE-p1
with kernel
FreeBSD caesium 14.2-RELEASE-p1 FreeBSD 14.2-RELEASE-p1 GENERIC amd64
keep panic with dmesg written below.

We have observed that the rate of panic is much lower after a Mikrotik peer was
shutdown. 


Fatal trap 12: page fault while in kernel mode
cpuid = 6; apic id = 0c
fault virtual address   = 0x10
fault code  = supervisor read data, page not present
instruction pointer = 0x20:0x80cfc37f
stack pointer   = 0x28:0xfe010c480c20
frame pointer   = 0x28:0xfe010c480cb0
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 = 0 (wg_tqg_6)
rdi:  rsi: fe010c4808c8 rdx: 82a16090
rcx:   r8: 82a16090  r9: 012c
rax:  rbx: f800057f6d70 rbp: fe010c480cb0
r10: 0006 r11: fe001ebd6468 r12: f800057f6d00
r13: f8007dd72000 r14: f800057f6d00 r15: 08080808
trap number = 12
panic: page fault
cpuid = 6
time = 1738843725
KDB: stack backtrace:
#0 0x80b8b88d at kdb_backtrace+0x5d
#1 0x80b3dc11 at vpanic+0x131
#2 0x80b3dad3 at panic+0x43
#3 0x81025a0b at trap_fatal+0x40b
#4 0x81025a56 at trap_pfault+0x46
#5 0x80ffc388 at calltrap+0x8
#6 0x80cfeb4b at ip_input+0x32b
#7 0x80c8387e at netisr_dispatch_src+0x9e
#8 0x83169683 at wg_deliver_in+0x363
#9 0x80b8a24e at gtaskqueue_run_locked+0x14e
#10 0x80b89ed2 at gtaskqueue_thread_loop+0xc2
#11 0x80af760f at fork_exit+0x7f
#12 0x80ffd3ee at fork_trampoline+0xe
Uptime: 2m24s
Dumping 866 out of 16343 MB:..2%..12%..21%..32%..41%..52%..61%..71%..82%..91%
Dump complete

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


[Bug 233578] Unprivileged local user can prevent other users logging in by locking utx.active

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233578

Dan Cross  changed:

   What|Removed |Added

 CC||cr...@gajendra.net

--- Comment #10 from Dan Cross  ---
This has come up for me recently, on a multiuser system where (by design) not
all of the accounts are completely trusted. Unprivileged users preventing
logins is unacceptable, but it would be a shame to de-permit access to
utx.active, thus making programs like `finger`, `w`, or `who` or other
consumers of the `getutxent` interface uninteresting.

The proposal in #4 seems reasonable; is there any chance this could be applied
any time soonish?

Btw, looking at the code in `pututxline`, the algorithm for updating lastlog
appears to be linear in the number of users on the system. We've got tens of
thousands of users, making this very slow; other systems use the uid as an
index into that file (which may be sparse as a result, but that's ok). Would it
be possible to do that here?

Also, we used to have a program that (effectively) tail -f'ed the wtmp file and
would print out a message when someone in a user-selectable list logged in or
out; our users enjoyed that. But there's no way to accommodate that in the
current framework, which is a shame. Part of this is due to the data format
being opaque, and part of it is inadequacies in the API (there's no way to use
e.g., `setutxdb` and then seek to the end of a file).  It's a bit of a shame.

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


[Bug 284621] panic during pkg upgrade

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284621

Bug ID: 284621
   Summary: panic during pkg upgrade
   Product: Base System
   Version: 15.0-CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: zarych...@plan-b.pwste.edu.pl

Created attachment 257300
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=257300&action=edit
backtrace

Yesterday, while upgrading pkg for CURRENT, I experienced a nice panic. It was
during a mass pkg upgrade (a few hundred packages were due to be upgraded). I
hope that the command "pkg upgrade" does not reload any kernel modules during
the upgrade process, but maybe it changed recently.
Indeed, the system that panicked was a bit older (it was 1500029) than the
system where pkg was built on in the repo (1500030), but from my experience
such pkg upgrade will rather not trigger panic, maybe some new apps will crash.

I am attaching the backtrace of the panic, the kernel that panicked was:
FreeBSD 15.0-CURRENT #14 main-n274227-448f54a3bfe6: Sun Dec 15 22:13:34 CET
2024
Unfortunately, it was kernel based on GENERRIC-NODEBUG.

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


[Bug 283726] wc(1) and other text utilities fail to read some pseudo-filesystem files

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283726

--- Comment #2 from Ricardo Branco  ---
The issue is produced by the kernel_sysctlbyname calls needed by
LINUX_RLIMIT_MSGQUEUE & LINUX_RLIMIT_SIGPENDING, contrary to the claim I made
in the initial comment.

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


[Bug 200744] serial driver issue under dell r220

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200744

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #4 from Mark Linimon  ---
^Triage: to submitter: does this problem still persist with later BIOS updates?

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


[Bug 199165] UEFI issues

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199165

Mark Linimon  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |Feedback Timeout

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


[Bug 199252] Fatal trap 12: page fault while in kernel mode

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199252

Mark Linimon  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Status|New |Closed

--- Comment #2 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 201620] mrsas ioctl failing

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201620

Mark Linimon  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Status|New |Closed

--- Comment #1 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 202017] weekly and monthly security check both check pkg audit

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202017

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org
  Component|misc|conf

--- Comment #1 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 196286] utf-8 variants of libc.cat missing

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196286

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #1 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 197321] syslogd randomly misses forwarding packets to remote host

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197321

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Resolution|--- |Overcome By Events
 Status|New |Closed

--- Comment #1 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 283273] bin/csh: tc.const.h built with host, not target, headers -- circular dependency

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283273

Ed Maste  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|ema...@freebsd.org

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


[Bug 266265] buildworld ends with error on 13.1-RELEASE PPC64

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266265

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #1 from Mark Linimon  ---
^Triage: does this still occur on a recent version of FreeBSD?

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


[Bug 283273] bin/csh: tc.const.h built with host, not target, headers -- circular dependency

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283273

Ed Maste  changed:

   What|Removed |Added

 Status|New |In Progress
URL||https://reviews.freebsd.org
   ||/D48880

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


[Bug 183047] [carp] carp stuck in INIT state

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183047

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|gleb...@freebsd.org
 CC||bugmeis...@freebsd.org

--- Comment #5 from Mark Linimon  ---
^Triage: to submitter and commenter: is this still a problem on recent versions
of FreeBSD?

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


[Bug 202127] Initial (first) login response is slow/delayed

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202127

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Status|New |Closed
 Resolution|--- |Overcome By Events

--- Comment #3 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 201457] Current temperature error (255° C)

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201457

Mark Linimon  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |Overcome By Events
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org

--- Comment #1 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 200973] Fatal trap 9: general protection fault while in kernel mode

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200973

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 CC|ead...@freebsd.org  |
 Status|New |Closed
 Resolution|--- |Overcome By Events

--- Comment #3 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 196845] devinfo does not present vital info (compared to sysctl)

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196845

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #1 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 200580] superfluous/unnecessary endhostent() does close(0) by accident. libc resolver dns fd close

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200580

Mark Linimon  changed:

   What|Removed |Added

 Resolution|--- |Works As Intended
 CC||bugmeis...@freebsd.org
 Status|Open|Closed

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


[Bug 200741] newsyslog, bzip2-runtime and additional runs

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200741

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #2 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 197013] Intel Ironlake in docked Dell E6510 will not display external monitor when using new VT

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197013

Mark Linimon  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|New |Closed
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org

--- Comment #1 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 197708] Allocation of PCI resources failed with options NEW_PCIB

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197708

Mark Linimon  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |Overcome By Events
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org

--- Comment #3 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 196609] install(1) doesn't set correct group when creating parent directories in directory hierarchy

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196609

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #3 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 199776] Quell non-determinisitc output in freebsd-update IDS reports.

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199776

Mark Linimon  changed:

   What|Removed |Added

   Keywords||feature

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


[Bug 200439] Executing 32 bit binary under 10.1/amd64

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200439

Mark Linimon  changed:

   What|Removed |Added

 Status|New |Closed
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Resolution|--- |Overcome By Events

--- Comment #1 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

Chattrapat Sangmanee  changed:

   What|Removed |Added

 CC||aomsi...@hotmail.co.th

--- Comment #46 from Chattrapat Sangmanee  ---
(In reply to Justin Hibbits from comment #43)

Can you tell me what is the commit id of that trap change? I own dual core
970MP and would like to see this working.

Also if you have any idea of what else could be a culprit please tell me. I can
test.

Thanks

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


[Bug 283726] wc(1) and other text utilities fail to read some pseudo-filesystem files

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283726

--- Comment #3 from Ricardo Branco  ---
Fix:

https://github.com/freebsd/freebsd-src/pull/1592

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


[Bug 284625] pf NAT with SMSC9512/9514 drops packets when RXCSUM is enabled (default setting)

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284625

Bug ID: 284625
   Summary: pf NAT with SMSC9512/9514 drops packets when RXCSUM is
enabled (default setting)
   Product: Base System
   Version: 14.2-RELEASE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: j...@eyb.com.br

The system under test is a Raspberry Pi 3B+, using the internal ethernet port,
which is connected to the USB bus. Here's the dmesg for the kernel module:

smsc0 on uhub1
smsc0:  on usbus1
smsc0: chip 0xec00, rev. 0002
miibus0:  on smsc0
smscphy0:  PHY 1 on miibus0
smscphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ue0:  on smsc0
smsc0: chip 0xec00, rev. 0002

and the usbconfig for the device:

ugen1.3:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)

Networking works fine on the host. When I set up some jails using Bastille,
with localhost networking (bastille0), I can send packets just fine (like
trying to "host mit.edu") and get a reply on the interface, but the jail does
not see the reply packet. This happens for both TCP and UDP. I get the logs
using this in pf.conf:

nat log(all) on $ext_if from  to any -> ($ext_if:0)

and then

tcpdump -i pflog0

I then did the exact same setup but connecting via a wifi interface (wlan0,
with ue0 disconnected) and it worked as expected (proper network access from
inside the jails, NAT working fine). I tried it with another external USB
ethernet adapter, and it also worked fine. So while debugging this, I tried
disabling RXCSUM on the ue0 interface, and the NATed reply packets instantly
started going through to the jails. So AFAICT there is some conflict between
the expected checksum and the computed one, and the packets are dropped during
the NAT reply processing.

Please let me know if you need any testing.

cheers,
jd

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


[Bug 167742] Update documentation for group 5, and newgrp 1

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167742

--- Comment #5 from Felix Johnson  ---
Update patch to -current.
Needs review.

https://reviews.freebsd.org/D48877

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


[Bug 284595] loader takes 36 seconds to reach beastie menu

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284595

--- Comment #4 from Peter Miller  ---
(In reply to Mark Linimon from comment #3)

I suppose I should have led with that.

Acer Swift Edge
SFA16-41-R7SU

sysctl -a hw.model
hw.model: AMD Ryzen 7 6800U with Radeon Graphics

uname -a
FreeBSD flyingdutchman 14.2-STABLE FreeBSD 14.2-STABLE
stable/14-n270278-81a8f67a5b55 GENERIC amd64

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


[Bug 284595] loader takes 36 seconds to reach beastie menu on Acer Swift Edge SFA16-41-R7SU

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284595

Mark Linimon  changed:

   What|Removed |Added

Summary|loader takes 36 seconds to  |loader takes 36 seconds to
   |reach beastie menu  |reach beastie menu on Acer
   ||Swift Edge SFA16-41-R7SU

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


[Bug 284625] pf NAT with SMSC9512/9514 drops packets when RXCSUM is enabled (default setting)

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284625

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|p...@freebsd.org

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


[Bug 163481] freebsd do not add itself to ping route packet

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163481

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Resolution|--- |Overcome By Events
 Status|Open|Closed

--- Comment #5 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 203363] sshd fails to start

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203363

Mark Linimon  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|New |Closed
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org

--- Comment #1 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 238921] ACPI error AE_NO_MEMORY prevents shutdown (power off)

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238921

Mark Linimon  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2025
   ||51

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


[Bug 205459] UK keyboard does not work on fresh install

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205459

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #1 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 210256] mv may delete files on case-preserving but case-insensitive filesystems

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210256

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #1 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 207188] gptzfsboot may choose wrong pool

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207188

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #5 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 204914] freebsd-update installs source too late

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204914

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #1 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 183406] gpart label not accessible after reseating disk

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183406

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #3 from Mark Linimon  ---
^Triage: to submitter: does this problem still occur on supported versions of
FreeBSD?

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


[Bug 184419] [carp] [vlan] carp does not detect member when using vlan

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184419

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #10 from Mark Linimon  ---
^Triage: to submitter: has this problem been fixed on more recent versions of
FreeBSD?

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


[Bug 162867] better zfs_cv_init

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162867

Mark Linimon  changed:

   What|Removed |Added

 Attachment #120118|file.txt|kcondvar.h.patch
   filename||
 Attachment #120118|0   |1
   is patch||

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


[Bug 162867] better zfs_cv_init

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162867

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #2 from Mark Linimon  ---
^Triage: properly label the attachment as a patch.

To submitter: does this patch still appertain to the latest ZFS sources?

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


[Bug 193857] dmesg :interface ahci.1 already present in the KLD 'kernel' but kldstat show nothing about ahci.ko

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193857

Mark Linimon  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |Works As Intended

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


[Bug 193386] [panic] resource_list_alloc: resource entry is busy

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193386

Mark Linimon  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|New |Closed
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 CC|sta...@freebsd.org  |

--- Comment #3 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 188549] Improve installation on serial console

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188549

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|sysinst...@freebsd.org
  Component|misc|bin

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


[Bug 186330] [libarchive] tar error containing fisrt '/' char and hard links

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186330

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #2 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 188014] [kerberos] FreeBSD 10 Looping detected inside krb5_get_in_tkt

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188014

Mark Linimon  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Overcome By Events
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org

--- Comment #4 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 190912] [libc] shmctl(2) get shared memory state returning error attached process number

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190912

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #4 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 186986] mount_nullfs(8): nullfs mount options broken

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186986

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #3 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 164145] [netisr] when one of netisr threads take 100% system is going to work unstable

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164145

Mark Linimon  changed:

   What|Removed |Added

 Status|Open|Closed
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Resolution|--- |Overcome By Events

--- Comment #2 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 165170] [panic] server reboot while pinging

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165170

Mark Linimon  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Overcome By Events
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org

--- Comment #3 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 164474] The system couldn't turn on a monitor connected via DisplayPort

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164474

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Resolution|--- |Overcome By Events
 Status|Open|Closed

--- Comment #2 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 164261] [nullfs] fix panic with NFS served from NULLFS

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164261

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #5 from Mark Linimon  ---
^Triage: to submitter: is this still a problem with recent versions of FreeBSD?

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


[Bug 164130] [netisr] broken netisr initialization

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=164130

Mark Linimon  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Status|Open|Closed

--- Comment #5 from Mark Linimon  ---
^Triage: apparently long ago overcome by events.

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


[Bug 172632] [headers] Unused structure in netconfig.h

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=172632

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #3 from Mark Linimon  ---
^Triage: does this still apply to supported versions of FreeBSD?

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


[Bug 169680] [netware] NLM and security flavors

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169680

Mark Linimon  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|Open|Closed
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org

--- Comment #2 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 173077] BIND slaves root and arpa zones on wrong servers

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173077

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #4 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 34239] tunefs(8) man page doesn't describe arguments.

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=34239

--- Comment #12 from Felix Johnson  ---
Update patch to -current.

https://reviews.freebsd.org/D48875

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


[Bug 179546] syslog(8)/newsyslog(8) don't handle years sanely

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=179546

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #2 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 184757] [suspend/resume] Resume fails on the X200 when the C3 power mode is available and engaged

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184757

Mark Linimon  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Status|Open|Closed

--- Comment #2 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 185374] [msdosfs] [panic] Unmounting msdos filesystem in a bad state causes kernel panic

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185374

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Status|Open|Closed
 Resolution|--- |Overcome By Events

--- Comment #5 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 180724] occasional file corruption when using cp(1)

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=180724

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Status|Open|Closed
 Resolution|--- |Overcome By Events

--- Comment #2 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 187258] [bxe] BCM57810 bxe(4) unstable/fails to initialize

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187258

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Status|Open|Closed
 Resolution|--- |Overcome By Events

--- Comment #3 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 188425] Frequent segfault with multithreaded fork

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188425

Mark Linimon  changed:

   What|Removed |Added

 Status|Open|Closed
   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Resolution|--- |Overcome By Events

--- Comment #2 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 189409] [kerberos] Looping detected inside krb5_get_in_tkt (FreeBSD 10 x64)

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189409

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|bugmeis...@freebsd.org
 Status|Open|Closed
 Resolution|--- |Overcome By Events

--- Comment #3 from Mark Linimon  ---
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.

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


[Bug 189745] [uart] ns8250 uart spin lock held too long

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189745

Mark Linimon  changed:

   What|Removed |Added

 CC||bugmeis...@freebsd.org

--- Comment #2 from Mark Linimon  ---
^Triage: is this still a problem on supported versions of FreeBSD?

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


[Bug 284616] nfsd thread count auto-tune do not respect MAXNFSDCNT

2025-02-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284616

Bug ID: 284616
   Summary: nfsd thread count auto-tune do not respect MAXNFSDCNT
   Product: Base System
   Version: 14.2-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: florian.mil...@laposte.net

Hello everyone,

When launching nfsd without the -n parameter a function called
get_tuned_nfsdcount set the number of threads to launch at start to (number of
cpu * 8) but do not check if this result is greater than MAXNFSDCNT (which is
256).
On a processor with 72 cores it makes nfsd launch 576 threads per nfsd, if you
have multiple nfsd (with jails for example) it grows very quickly.

This problem do not appear if you manually set the number of threads through
the -n command line parameter to nfsd.

It would seem this regression appeared in commit
ae3e3df45c75ba60ec2cd2d425e4921bf2a6321d (or SVN revision 282272) nearly 10
years ago.

A patch like this one should be enough to restore this check :

diff --git a/usr.sbin/nfsd/nfsd.c b/usr.sbin/nfsd/nfsd.c
index c1995580e142..cb506a4b1740 100644
--- a/usr.sbin/nfsd/nfsd.c
+++ b/usr.sbin/nfsd/nfsd.c
@@ -1033,6 +1033,8 @@ get_tuned_nfsdcount(void)
tuned_nfsdcnt = DEFNFSDCNT;
} else {
tuned_nfsdcnt = ncpu * 8;
+   if (tuned_nfsdcnt > MAXNFSDCNT)
+   tuned_nfsdcnt = MAXNFSDCNT;
}
return tuned_nfsdcnt;
 }

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