[Bug 265761] [patch] rtadvd(8) should also deprecate prefix on shutdown

2022-09-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265761

Daniel Ponte  changed:

   What|Removed |Added

 CC||ami...@gmail.com

--- Comment #1 from Daniel Ponte  ---
I am very interested in this patch. Is there a reason this is not already done?
Does this run afoul of the RFCs in some way?

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


[Bug 265761] [patch] rtadvd(8) should also deprecate prefix on shutdown

2022-09-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265761

--- Comment #2 from Daniel Ponte  ---
Looking more closely at Linux's radvd, they have it as a configuration option
(DeprecatePrefix). This should probably similarly be implemented as a
per-interface config.

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


[Bug 266224] Could some sort of file transfer program be put in /rescue?

2022-09-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266224

Bug ID: 266224
   Summary: Could some sort of file transfer program be put in
/rescue?
   Product: Base System
   Version: 12.2-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: free...@gushi.org

Hey there,

I run a network of DNS servers, out there in cold unforgiving data centers in
places in the world where remote hands are hard to come by and the only
connectivity you get sometimes is a serial console.  Often you'll get clueful
techs who will reboot a machine for you but not much more.

Numerous times, I've been bitten by freebsd-update segfaulting and leaving me
with an unusable system that won't survive a reboot (either because of a
failure to replace ld.so or because of a full /var or / or other partition).

At that point you're logged in to a system over ssh, you cannot ssh in a second
time, and you need to recover the system quickly.

The only real fix is to copy binaries (or a base.txz) from another machine
using the statically linked binaries in /rescue.  And other than nc (which
works, but has no progress indicator and no real checks), there's no easy way
to get files onto and off a system.

I get it, scp and ssh have heavy crypto overhead, as does fetch at this point,
but a fetch-lite that only spoke HTTP and FTP would be super useful, as would a
copy of old school ftp.  Or, you know, maybe just a statically linked scp/ssh
*is* the right answer here.  (Busybox is a cool idea but it has the GPL issue).

There's no patch for this, it's more an enhancement request.

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


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

2022-09-04 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|187015 | agpgart: Panic make_dev_credv: bad si_name (error 
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   
New |265632 | sound: add Lenovo Legion 5 speakers sound output  
Open|179832 | manual page of mac_from_text suggests incorrect f 

48 problems total for which you should take action.


[Bug 266145] [Intel Alder Lake] Crashes on CURRENT vfs

2022-09-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145

rkober...@gmail.com changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People

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


[Bug 266145] [Intel Alder Lake] Crashes on CURRENT vfs

2022-09-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145

Amar Takhar  changed:

   What|Removed |Added

 CC||v...@darkbeer.org

--- Comment #3 from Amar Takhar  ---
It's the same for me on my system Intel i9-12900KF.  Disabling soft updates
didn't make much of a change for me though it did take a bit longer to crash 
Once it hits somewhere it doesn't like on the filesystem it consistently fails
even across reboots it seems to be extremely random.  Disabling the E-core
fixes all the issues.

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


[Bug 266145] [Intel Alder Lake] Crashes on CURRENT vfs

2022-09-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145

--- Comment #4 from rkober...@gmail.com ---
(In reply to Amar Takhar from comment #3)
I'm reasonably sure that it is not that it has a problem with the file system.
It's likely a race of some sort caused by the different performance of the
cores. When a process moves between different sped cores, it looks like things
go wonky, probably in the vfs or maybe the UFS code.

I now have about 7 dumps, though only one since disabling soft updates that
look tie to vfs.

I can make the cores available as they are all from a system being prepped for
use with no sensitive data files.

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