[Bug 263838] please bundle unbound-event.h

2022-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263838

Fernando Apesteguía  changed:

   What|Removed |Added

  Flags||maintainer-feedback?(yuri@f
   ||reebsd.org)
 CC||y...@freebsd.org

--- Comment #12 from Fernando Apesteguía  ---
(In reply to Andrew Cagney from comment #11)
Including maintainer in the discussion.

I don't see security/libreswan failing in the cluster and the port depends on
dns/unbound. Does it fail for you?

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


[Bug 255047] race bug with mount generating same fsid for different mount points

2022-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255047

--- Comment #2 from Olivier Cochard  ---
Source of the problem in vfs_getnewfsid() in sys/kern/vfs_subr.c that has this
comment:

  * Keep in mind that several mounts may be running in parallel.  Starting
  * the search one past where the previous search terminated is both a
  * micro-optimization and a defense against returning the same fsid to
  * different mounts.


This protection doesn't work here.

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


[Bug 263433] SEE ALSO section improvements for tuning(7), fsck_ffs(8), tunefs(8) …

2022-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263433

Gordon Bergling  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|g...@freebsd.org
 Status|New |In Progress
 CC||g...@freebsd.org

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


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

2022-11-06 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 |198797 | [PATCH] Added an option to install BSDstats to bs 
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|207940 | stand/efi/boot1: Add boot partition selection 
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  
New |260138 | TPM2 Support in bootloader / kernel in order to r 
New |261306 | Geli rc.d script does not support insertion of US 
New |262957 | mpr(4), mps(4): change formally to formerly   
Open|179832 | manual page of mac_from_text suggests incorrect f 

46 problems total for which you should take action.


[Bug 263838] please bundle unbound-event.h

2022-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263838

--- Comment #11 from Andrew Cagney  ---
> I'm afraid that if you want ubound-event.h in 13.1 you will need to checkout 
> the sources for the release and configure with --enable-event-api.

So libreswan should build and link against a private version of unbound?  I'm
guessing but wouldn't bundling a private copy of a security sensitive library
such as unbound be a big no-no when it comes to "ports" (FreeBSD's packaging
guidelines).

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


[Bug 263838] please bundle unbound-event.h

2022-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263838

--- Comment #10 from Fernando Apesteguía  ---
(In reply to Andrew Cagney from comment #9)
I doubt we will bundle that file being marked as unstable. Would the provided
workaround be useful for you?

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


[Bug 267028] General protection fault kernel panic immediately after kldload amdgpu

2022-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028

--- Comment #13 from George Mitchell  ---
As of today, with version drm-510-kmod-5.10.113_8:

1. I can reliably prevent a crash by booting to single user mode, manually
kldloading amdgpu, and continuing (typing control-d).  dmesg then reports:

[drm] amdgpu kernel modesetting enabled.
drmn0:  on vgapci0
vgapci0: child drmn0 requested pci_enable_io
vgapci0: child drmn0 requested pci_enable_io
[drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x1458:0xD000 0xC8).
drmn0: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
[drm] register mmio base: 0xFE60
[drm] register mmio size: 524288
[drm] add ip block number 0 
[drm] add ip block number 1 
[drm] add ip block number 2 
[drm] add ip block number 3 
[drm] add ip block number 4 
[drm] add ip block number 5 
[drm] add ip block number 6 
[drm] add ip block number 7 
[drm] add ip block number 8 
drmn0: successfully loaded firmware image 'amdgpu/raven_gpu_info.bin'
[drm] BIOS signature incorrect 44 f
drmn0: Fetched VBIOS from ROM BAR
amdgpu: ATOM BIOS: 113-RAVEN-111
drmn0: successfully loaded firmware image 'amdgpu/raven_sdma.bin'
[drm] VCN decode is enabled in VM mode
[drm] VCN encode is enabled in VM mode
[drm] JPEG decode is enabled in VM mode
[drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is
9-bit
drmn0: VRAM: 2048M 0x00F4 - 0x00F47FFF (2048M used)
drmn0: GART: 1024M 0x - 0x3FFF
drmn0: AGP: 267419648M 0x00F8 - 0x
[drm] Detected VRAM RAM=2048M, BAR=2048M
[drm] RAM width 128bits DDR4
[TTM] Zone  kernel: Available graphics memory: 3100774 KiB
[TTM] Zone   dma32: Available graphics memory: 2097152 KiB
[TTM] Initializing pool allocator
[drm] amdgpu: 2048M of VRAM memory ready
[drm] amdgpu: 3072M of GTT memory ready.
[drm] GART: num cpu pages 262144, num gpu pages 262144
[drm] PCIE GART of 1024M enabled (table at 0x00F40090).
drmn0: successfully loaded firmware image 'amdgpu/raven_asd.bin'
drmn0: successfully loaded firmware image 'amdgpu/raven_ta.bin'
drmn0: successfully loaded firmware image 'amdgpu/raven_pfp.bin'
drmn0: successfully loaded firmware image 'amdgpu/raven_me.bin'
drmn0: successfully loaded firmware image 'amdgpu/raven_ce.bin'
drmn0: successfully loaded firmware image 'amdgpu/raven_rlc.bin'
drmn0: successfully loaded firmware image 'amdgpu/raven_mec.bin'
drmn0: successfully loaded firmware image 'amdgpu/raven_mec2.bin'
amdgpu: hwmgr_sw_init smu backed is smu10_smu
drmn0: successfully loaded firmware image 'amdgpu/raven_vcn.bin'
[drm] Found VCN firmware Version ENC: 1.12 DEC: 2 VEP: 0 Revision: 1
drmn0: Will use PSP to load VCN firmware
[drm] reserve 0x40 from 0xf47fc0 for PSP TMR
drmn0: RAS: optional ras ta ucode is not available
drmn0: RAP: optional rap ta ucode is not available
[drm] kiq ring mec 2 pipe 1 q 0
[drm] DM_PPLIB: values for F clock
[drm] DM_PPLIB:  40 in kHz, 3649 in mV
[drm] DM_PPLIB:  933000 in kHz, 4074 in mV
[drm] DM_PPLIB:  120 in kHz, 4399 in mV
[drm] DM_PPLIB:  1333000 in kHz, 4399 in mV
[drm] DM_PPLIB: values for DCF clock
[drm] DM_PPLIB:  30 in kHz, 3649 in mV
[drm] DM_PPLIB:  60 in kHz, 4074 in mV
[drm] DM_PPLIB:  626000 in kHz, 4250 in mV
[drm] DM_PPLIB:  654000 in kHz, 4399 in mV
[drm] Display Core initialized with v3.2.104!
[drm] VCN decode and encode initialized successfully(under SPG Mode).
drmn0: SE 1, SH per SE 1, CU per SH 11, active_cu_number 8
[drm] fb mappable at 0x60BCA000
[drm] vram apper at 0x6000
[drm] size 8294400
[drm] fb depth is 24
[drm]pitch is 7680
VT: Replacing driver "vga" with new "fb".
start FB_INFO:
type=11 height=1080 width=1920 depth=32
pbase=0x60bca000 vbase=0xf80060bca000
name=drmn0 flags=0x0 stride=7680 bpp=32
end FB_INFO
drmn0: ring gfx uses VM inv eng 0 on hub 0
drmn0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
drmn0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
drmn0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
drmn0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
drmn0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
drmn0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
drmn0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
drmn0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
drmn0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
drmn0: ring sdma0 uses VM inv eng 0 on hub 1
drmn0: ring sdma0 uses VM inv eng 0 on hub 1
drmn0: ring vcn_dec uses VM inv eng 1 on hub 1
drmn0: ring vcn_enc0 uses VM inv eng 4 on hub 1
drmn0: ring vcn_enc1 uses VM inv eng 5 on hub 1
drmn0: ring jpeg_dec uses VM inv eng 6 on hub 1
vgapci0: child drmn0 requested pci_get_powerstate
sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)!
[drm] Initialized amdgpu 3.40.0 20150101 for drmn0 on minor 0

Is the sysctl_warn_reuse message anything to worry about?

2. Adding amdgpu to the kldlist in rc.conf still crashes more often than not,
as previously reported.

3. Attempting to load amdgpu via /boot/loader.conf appears to 

[Bug 267596] Support UTF-8 dns resolution

2022-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267596

Yonas Yanfa  changed:

   What|Removed |Added

URL||https://blog.cloudflare.com
   ||/non-latinutf8-domains-now-
   ||fully-supported/

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


[Bug 267596] Support UTF-8 dns resolution

2022-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267596

Bug ID: 267596
   Summary: Support UTF-8 dns resolution
   Product: Base System
   Version: Unspecified
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: yonas.ya...@gmail.com

`host マリウス.com` and `fetch https://マリウス.com` does not work.

It works on Ubuntu (22.10).

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


[Bug 213178] [libc] resolv "asked for IN A got RRSIG" syslog spamming with DNSSEC bit set

2022-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213178

axel@chaos1.de changed:

   What|Removed |Added

 CC||axel@chaos1.de

--- Comment #1 from axel@chaos1.de ---
This hurts me everyday in 13.1:
- - -
exim[5671] gethostby*.gethostanswer: asked for "some_fqdn IN ", got type
"RRSIG"
- - -

If this is the same problem, why can't it be fixed?
There exist a proposal from 2016.

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