[Bug 279381] FreeBSD 13.3-RELEASE breaks isp driver with Qlogic QLE2692 16Gb fibre channel cards

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

drkspc  changed:

   What|Removed |Added

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

--- Comment #7 from drkspc  ---
We updated all of our servers to 13.4 by now and everything is running fine.
I'll close the issue for now. Feel free to reopen in case of ongoing issues in
this context.

-- 
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-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282112

Bug ID: 282112
   Summary: release: latest GCE images do not work in Cirrus CI
   Product: Base System
   Version: 15.0-CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: asom...@freebsd.org

Cirrus CI is a major user of our GCE images.  But the latest 15.0-CURRENT
images do not work.  A summary of their error messages:

freebsd-15-0-current-amd64-ufs-20240905:
Agent is not responding!
freebsd-15-0-current-amd64-ufs-20240912:
ld-elf.so.1: Shared object "libmd.so.7" not found, required by "pkg"
freebsd-15-0-current-amd64-ufs-20240919:
ld-elf.so.1: Shared object "libmd.so.7" not found, required by "pkg"
freebsd-15-0-current-amd64-ufs-20240926:
ld-elf.so.1: Shared object "libmd.so.7" not found, required by "pkg"
freebsd-15-0-current-amd64-ufs-20241003:
Agent is not responding!
freebsd-15-0-current-amd64-ufs-20241010:
Agent is not responding!

Note that images prior to 20241003 _used_ to work.  So those errors are
probably coming from newer packages.

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


[Bug 274522] VM image's rc.conf has many repeated lines

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

Mark Johnston  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|cperc...@freebsd.org
 Status|Open|Closed
 Resolution|--- |FIXED
 CC||ma...@freebsd.org

--- Comment #3 from Mark Johnston  ---
This was fixed by commit 97bd53ef4d20b7d15e0b0976e885af9438f5637e.  The rc.conf
in FreeBSD-14.1-RELEASE-arm64-aarch64-zfs.raw doesn't have any duplicated
lines.

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


[Bug 271607] 14.0-RELEASE metabug

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

Bug 274522 Summary: VM image's rc.conf has many repeated lines
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274522

   What|Removed |Added

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

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


[Bug 262655] [13.1-BETA2] cosmetic arm64 qcow2 image has duplicate lines in /etc/rc.conf

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

Mark Johnston  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |DUPLICATE

--- Comment #3 from Mark Johnston  ---


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

-- 
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-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282112

Mark Linimon  changed:

   What|Removed |Added

   Keywords||regression

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


[Bug 282115] GELI + QAT - 8955 performance is less than software encoding for block device acceleration

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

Mark Linimon  changed:

   What|Removed |Added

   Keywords||performance

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


[Bug 271607] 14.0-RELEASE metabug

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

Bug 273661 Summary: freebsd-update install: ///usr/include/c++/v1/__string 
exists but is not a directory
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273661

   What|Removed |Added

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

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


[Bug 271607] 14.0-RELEASE metabug

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

Bug 273661 Summary: freebsd-update install: ///usr/include/c++/v1/__string 
exists but is not a directory
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273661

   What|Removed |Added

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

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


[Bug 243177] open(2): Add O_CREATFIFO flag

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

--- Comment #5 from Ronald F. Guilmette  ---
At this point, after waiting more than 4.75 years for anyone to even just look
at this PR, I'm not inclined to spend much time debating the merits of
implementing something like the suggested O_CREATFIFO flag.  I will just offer
the (closing?) observation that the O_CREAT flag was created for a very good
reason and that reason, it seems to me, must necessarily apply equally well to
both regular files AND fifos.  I am not seeing a clear argument to the
contrary.

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


[Bug 282073] newsyslog(8): options in /etc/defaults/rc.conf not consistent with /etc/crontab

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

Michael Osipov  changed:

   What|Removed |Added

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

--- Comment #4 from Michael Osipov  ---
Thank you Ed, you are right. Reviewing this again this isn't a problem. It will
be a problem if then default of "-CN" is changed, but that is out of scope
here.

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


[Bug 281218] Quectel LTE MODEM not working anymore

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

Dean  changed:

   What|Removed |Added

 CC||dean.hom...@gmail.com

--- Comment #17 from Dean  ---
I'm also running into the same issue using a Sierra EM7455 (Dell DW5811e
flashed to generic EM7455) with OPNsense 24.7 (FreeBSD 14.1).

Re-installing OPNsense 24.1 (FreeBSD 13.2-RELEASE-p11) resolved the issue for
me.

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


[Bug 282115] GELI + QAT - 8955 performance is less than software encoding for block device acceleration

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

Bug ID: 282115
   Summary: GELI + QAT - 8955 performance is less than software
encoding for block device acceleration
   Product: Base System
   Version: 14.1-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: ja...@elstone.net

Created attachment 254268
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254268&action=edit
Memory Disk QAT + Geli Test Steps

Having installed an Intel QAT 8955 card and tested performance, there is a
significant decrease in speed with the QAT card enabled compared to software
crypto. 

The CPU used for these offline tests was an old Intel(R) Xeon(R) CPU E5-2403 0
@ 1.80GHz that has the AES-NI instruction set. Fresh install of FreeBSD 14.1-p5
was used for each test, that than a custom kernel with AES-NI removed.

The disk used to test against in the results below is a WD BLACK SN750 SE in a
PCI slot adapter. The DD speed to a mounted volume for this disk is 1532 MB/s.

The script to generate these results is attached for referencem but uses a
memory disk for testing maximal throughput.

The /boot/loader.conf is:
 dev.qat.0.cfg_services = "sym;asym"
 qat_dh895xcc_fw_load="YES"
 qat_load="YES"
 cryptodev_load="YES"

Parameters: A:HMAC/SHA256 E:AES-CBC L:256
Crypto: hardware
irq85: qat0:b0  77310798   1368
irq86: qat0:b1 120404887   2130
DD - DISK_BLK_SIZE:4096 DD_BLK_SIZE:8388608 DD_COUNT:25
** write speed: (66,475,964 bytes/sec)
irq85: qat0:b0  77310798   1368
irq86: qat0:b1 120833699   2137

Parameters: A:HMAC/SHA256 E:AES-XTS L:256 BS:4096
Crypto: hardware
irq85: qat0:b0  77310798   1367
irq86: qat0:b1 121389848   2147
DD - DISK_BLK_SIZE:4096 DD_BLK_SIZE:8388608 DD_COUNT:25
** Write speed: (61,894,122 bytes/sec)
irq85: qat0:b0  77310798   1367
irq86: qat0:b1 121841632   2155


Parameters: A:HMAC/SHA256 E:AES-CBC L:256 BS:4096
Crypto: software
DD - DISK_BLK_SIZE:4096 DD_BLK_SIZE:8388608 DD_COUNT:25
** write speed: (110,486,470 bytes/sec)

Parameters: A:HMAC/SHA256 E:AES-XTS L:256
Crypto: software
DD - DISK_BLK_SIZE:4096 DD_BLK_SIZE:8388608 DD_COUNT:25
** write speed: (102,362,135 bytes/sec)

The above shows a drop in performance of 40%.

Additionally when using the attached memory disk example, the throughput of
this system tops out at ~135Mbps when writing to a mounted encrypted ramdisk
UFS volume, with the 4 cores operating at about 25% each.

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


[Bug 264030] [tracking] 13.1-RELEASE issue reports

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

Bug 264032 Summary: riscv VM images are empty/blank
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264032

   What|Removed |Added

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

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


[Bug 282096] Makefile.inc1 never sets MK_CLEAN to "yes"

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

--- Comment #2 from Don Lewis  ---
OK, the make magic is why grepping the source tree didn't find MK_CLEAN getting
set.  Caution, contents under pressure, no user serviceable parts inside.

The command line options section in Makefile.inc1 needs to be updated for the
behavior change.

I'm still puzzled why make -V doesn't show MK_CLEAN getting set:

# pwd
/usr/src
# make -V MK_CLEAN

# make -D WITH_CLEAN -V MK_CLEAN buildworld

# make -D CLEAN -V MK_CLEAN buildworld

#

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


[Bug 282096] Makefile.inc1 never sets MK_CLEAN to "yes"

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

--- Comment #1 from Ed Maste  ---
MK_CLEAN is set by share/mk/src.opts.mk and src.conf(5), and recently switched
to avoid doing clean builds by default. See the 20240729 entry in UPDATING:

20240729:
The build now defaults to WITHOUT_CLEAN - i.e., no automatic clean
is performed at the beginning of buildworld or buildkernel.  The
WITH_CLEAN src.conf(5) knob can be used to restore the previous
behaviour.

If you encounter incremental build issues, please report them to the
freebsd-current mailing list so that a special-case dependency can be
added, if necessary.

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


[Bug 282115] GELI + QAT - 8955 performance is less than software encoding for block device acceleration

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

Mark Johnston  changed:

   What|Removed |Added

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

--- Comment #1 from Mark Johnston  ---
While a 40% hit is steep, it's not totally surprising that QAT is worse here. 
The general tradeoff of using an offload engine is that crypto request latency
will go up, but you spend less CPU resources, and offload engines, QAT in
particular, can service many requests in parallel.  That is, if your benchmark
is to dispatch one crypto request at a time, wait for it to complete, and
measure how long that takes, handling requests on the CPU will probably win
out.

Here it looks like you're dd'ing to a GELI disk device, so each I/O is getting
executed serially, i.e., you're not getting any advantage from parallelism.  Is
that right?  What kinds of numbers do you get if there is a lot of concurrent
background I/O load (e.g., from running dd loops in the background) or CPU load
(e.g., from running some CPU-intensive process, like a kernel build)?

How much CPU usage do you get in your benchmark with and without QAT?

Have you tried similar experiments using the QAT driver on Linux?  More
generally, what kinds of results were you expecting?

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