Problem reports for b...@freebsd.org that need special attention

2023-09-03 Thread bugzilla-noreply
To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |197876 | [devfs] an error in devfs leads to data loss and  
New |202362 | ntp: restore refclocks selection (10.2-RELEASE re 
New |202740 | vi/ex string substitution problem when there is m 
New |204097 | witness_initialize() does not perform bound check 
New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi 
New |209213 | UEFI Loader shows only black screen with Nvidia G 
New |210804 | installerconfig - using ZFS create in custom scri 
New |223470 | freebsd-update: Cannot identify running kernel (/ 
New |230620 | "install -d" issue
New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( 
New |252123 | fetch(3): Fix wrong usage of proxy when request i 
Open|177821 | sysctl: Some security.jail nodes are funky, dupli 
Open|182466 | [headers] [patch] make  self-contained  
Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf 
Open|192573 | Add ps(1) option: Print process start time in sec 
Open|194925 | [pf] [ifconfig] interface group keywords do not w 
Open|197921 | scheduler: Allow non-migratable threads to bind t 
Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4)  
Open|206649 | cyapa(4): Add common gestures for Cypress APA I2C 
Open|212608 | sockstat(1) and lsof(8) can not identity the owne 
Open|220246 | syslogd does not send RFC3164-conformant messages 
Open|221305 | Mouse cursor loss when moving cursor while loadin 
Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL 
Open|221854 | makefs: Reject UFS labels that are too long to fi 
Open|226893 | freebsd-update: Support patchlevel argument for f 
Open|231810 | [build] release always fails with "mkimg: partiti 
Open|233578 | Unprivileged local user can prevent other users l 
Open|233988 | freebsd-update: Improve progress output on termin 
Open|236718 | system panics with message: vm_fault_hold: fault  
Open|237287 | moused(8) ignores button release events in virtua 
Open|237924 | Possible infinite loop in function empty_aux_buff 
Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana 
Open|238486 | Possible buffer overflow bug in sc_allocate_keybo 
Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 
Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c 
Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea 
Open|241697 | i915kms: Kernel panic loading module on custom ke 
Open|247132 | Fix build error: use of undeclared identifier 'cp 
Open|248352 | mfi(4): Remove RAID map sync functionality
Open|257149 | CFLAGS not passed to whole build  

40 problems total for which you should take action.


[Bug 273543] FreeBSD-15 kernel panic when the amdtemp device is in the kernel

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273543

Mitchell Horne  changed:

   What|Removed |Added

 CC||mho...@freebsd.org

--- Comment #2 from Mitchell Horne  ---
Please share the panic message and backtrace. Thank you.

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


[Bug 273539] VLAN issue after upgrading from stable/13 to main or stable/14 - kernel without COMPAT_FREEBSD12

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273539

Mark Linimon  changed:

   What|Removed |Added

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

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


[Bug 273544] [panic] FreeBSD 14 panic when kernel compiled with amdtemp

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273544

--- Comment #3 from Martin Matuska  ---
In the "Kernel panic screen log" I have already attached you have these bits at
the beginning.

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


[Bug 273401] strverscmp(3)'s HISTORY claims it was added in 14.0

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273401

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

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

commit 4c509ef95c5d2b359b7276487a05f5e9ce911e3d
Author: Mina Galić 
AuthorDate: 2023-08-31 11:50:17 +
Commit: Konstantin Belousov 
CommitDate: 2023-09-03 16:06:36 +

libc: fix history for strverscmp(3) and versionsort(3)

PR: 273401
Approved by:re (gjb)

(cherry picked from commit 09ec5e67a7a6605e5a58a2e3e82dab243a90609a)

 lib/libc/gen/scandir.3   | 4 ++--
 lib/libc/string/strverscmp.3 | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

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


[Bug 273543] FreeBSD-15 kernel panic when the amdtemp device is in the kernel

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273543

--- Comment #1 from Vladimir Druzenko  ---
https://cgit.freebsd.org/src/commit/?id=9a7add6d01f3c5f7eba811e794cf860d2bce131d

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


[Bug 273544] [panic] FreeBSD 14 panic when kernel compiled with amdtemp

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273544

Vladimir Druzenko  changed:

   What|Removed |Added

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

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


[Bug 273543] FreeBSD-15 kernel panic when the amdtemp device is in the kernel

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273543

Vladimir Druzenko  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2735
   ||44
 CC||v...@freebsd.org

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


[Bug 273544] [panic] FreeBSD 14 panic when kernel compiled with amdtemp

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273544

Warner Losh  changed:

   What|Removed |Added

 CC||i...@freebsd.org

--- Comment #2 from Warner Losh  ---
can you attach the first bit of your dmesg? I have

[1.01] CPU: AMD EPYC 7551 32-Core Processor (2000.05-MHz
K8-class CPU)
[1.02]   Origin="AuthenticAMD"  Id=0x800f12  Family=0x17  Model=0x1 
Stepping=2
[1.03]  
Features=0x178bfbff
[1.04]  
Features2=0x7ed8320b
[1.05]   AMD Features=0x2e500800
[1.06]   AMD
Features2=0x35c233ff
[1.07]   Structured Extended
Features=0x209c01a9
[1.08]   XSAVE Features=0xf
[1.09]   AMD Extended Feature Extensions ID
EBX=0x1007
[1.10]   SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
[1.11]   TSC: P-state invariant, performance statistics

and don't see the problem... I have a few AMD systems at work that might be the
same gen as you have that shows the problem..

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


[Bug 273544] [panic] FreeBSD 14 panic when kernel compiled with amdtemp

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273544

--- Comment #1 from Martin Matuska  ---
Created attachment 244614
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=244614=edit
Kernel configuration file

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


[Bug 273544] [panic] FreeBSD 14 panic when kernel compiled with amdtemp

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273544

Bug ID: 273544
   Summary: [panic] FreeBSD 14 panic when kernel compiled with
amdtemp
   Product: Base System
   Version: 14.0-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: m...@freebsd.org

Created attachment 244613
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=244613=edit
Kernel panic screen log

My ZEN 2 system panics when compiled with amdtemp(8) and amdsmn(8). When doing
a kldload at boot time everything goes fine.

Maybe does the order of compilation play a role?

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


[Bug 273543] FreeBSD-15 kernel panic when the amdtemp device is in the kernel

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273543

Bug ID: 273543
   Summary: FreeBSD-15 kernel panic when the amdtemp device is in
the kernel
   Product: Base System
   Version: 15.0-CURRENT
  Hardware: amd64
OS: Any
Status: New
  Keywords: crash
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: gljennj...@gmail.com

Including amdtemp in the kernel configuration file for FreeBSD-15 results in a
kernel panic at boot time.

A git bisect identified commit 9a7add6d01f3c5f7eba811e794cf860d2bce131d as the
cause.  This commit was made by Colin Percival on August 19, 2023, after
FreeBSD-15 was created, so this probably only affects FreeBSD-15 itself.

A user reported on current.freebsd.org that reverting this commit resolves the
panic problem.

A workaround is to kldload amdsmn.ko and amdtemp.ko.

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


[Bug 273539] VLAN issue after upgrading from stable/13 to main or stable/14 - kernel without COMPAT_FREEBSD12

2023-09-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273539

Bug ID: 273539
   Summary: VLAN issue after upgrading from stable/13 to main or
stable/14 - kernel without COMPAT_FREEBSD12
   Product: Base System
   Version: 14.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: herb...@gojira.at

After updating from stable/13 to (main and later to) stable/14
net/mpd5 only connects to my ISP (VDSL with VLAN) if I enable "options
COMPAT_FREEBSD12" in my kernel. Without I get only:

Aug 30 15:08:06 gw mpd[59876]: [L1] PPPoE connection timeout after 9 seconds
Aug 30 15:08:06 gw mpd[59876]: [L1] Link: DOWN event
Aug 30 15:08:06 gw mpd[59876]: [L1] LCP: Down event
Aug 30 15:08:06 gw mpd[59876]: [L1] Link: reconnection attempt 1 in 7 seconds
Aug 30 15:08:14 gw mpd[59876]: [L1] Link: reconnection attempt 1
Aug 30 15:08:14 gw mpd[59876]: [L1] PPPoE: Connecting to ''
Aug 30 15:08:23 gw mpd[59876]: [L1] PPPoE connection timeout after 9 seconds
Aug 30 15:08:23 gw mpd[59876]: [L1] Link: DOWN event
Aug 30 15:08:23 gw mpd[59876]: [L1] LCP: Down event
[..]


Without "COMPAT_FREEBSD12" vlanproto = 0x.
If I run "ifconfig vlan31 vlanproto 802.1q" mpd5 works.

According to ifconfig(8) 802.1q is the default vlanproto.

Maybe this commit is related:

commit afbb64f1d85b7d8c2938031c3567946b5d10da4f
Author: Alexander V. Chernikov
Date:   Sun Apr 11 17:47:03 2021 +0100

  Fix vlan creation for the older ifconfig(8) binaries.

  Reported by:allanjude
  MFC after:  immediately

?


To reproduce: build and run the following kernel:

include GENERIC
ident TEST
nooptions COMPAT_FREEBSD12

stable/13:

# ifconfig vlan99 create
 ==> vlanproto: 0x
# ifconfig vlan99 vlan 99 vlandev igb0
 ==> vlanproto: 802.1q
# ifconfig vlan99 destroy
# ifconfig vlan99 create vlan 99 vlandev igb0
 ==> vlanproto: 802.1q

On stable/14 or main:

# ifconfig vlan99 create
 ==> vlanproto 0x
# ifconfig vlan99 vlan 99 vlandev igb0
 ==> vlanproto 0x
# ifconfig vlan99 create vlan 99 vlandev igb0
 ==> vlanproto: 802.1q

I guess that's why the following lines in my /etc/rc.conf no longer
work on stable/14 or main.

cloned_interfaces="vlan99"
ifconfig_vlan99="vlan 99 vlandev igb0"

I have to replace the ifconfig line with:

ifconfig_vlan99="vlan 99 vlandev igb0 vlanproto 802.1q"

It also works if I remove the following lines in sys/net/if_vlan.c:

1110 #ifdef COMPAT_FREEBSD12
1113 #endif

2265 #ifdef COMPAT_FREEBSD12
2268 #endif

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