From nobody Mon Aug 19 12:47:30 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WnXSD4B45z5Syhp for ; Mon, 19 Aug 2024 12:47:40 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [IPv6:2a01:4f8:171:f902::5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WnXSC6Gqvz4fsX for ; Mon, 19 Aug 2024 12:47:39 +0000 (UTC) (envelope-from crest@rlwinm.de) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of crest@rlwinm.de designates 2a01:4f8:171:f902::5 as permitted sender) smtp.mailfrom=crest@rlwinm.de Received: from [IPV6:2001:9e8:954:3f00:242a:3320:3607:8c07] (unknown [IPv6:2001:9e8:954:3f00:242a:3320:3607:8c07]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id D0A6B27083 for ; Mon, 19 Aug 2024 12:47:31 +0000 (UTC) Message-ID: Date: Mon, 19 Aug 2024 14:47:30 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: a zfs thank you :) To: freebsd-current@freebsd.org References: Content-Language: en-US From: Jan Bramkamp In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.29 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[rlwinm.de]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4WnXSC6Gqvz4fsX On 31.07.24 17:02, void wrote: > Hi, > > I was pleasantly surprised when I installed a new [1] zfs-on-root > -current > to rpi4 that when adduser was invoked, I was given the option to > encrypt the homedir. This is a great feature for my context [2]. > > It doesn't automount on boot but I think this is more of a feature > rather than a bug. One can have a different password to the GELI one used > to boot up the whole system. > > I have not tested yet whether one can have the user, once logged in, > mount > their homedir with doas(1). Right now, I mount the homedir like so: > > zfs load-key -a (prompts for password) > zfs mount -a > > as root. > > I could I guess make a doas line for the user for zfs load-key -r > zfsfile/system. > Can anyone suggest any better ideas please? There is the pam_zfs_key.so PAM session module that should do exactly what you're looking for if your users login with a password. It should similar to the pam_ssh.so module if you're already familiar with that one. Unless users provide the password there isn't much file system or disk encryption can do for you against hardware theft since the Raspberry Pi doesn't have any secure key storage nor would the kernel be able to know when it has been stolen and stop auto-loading the keys. From nobody Mon Aug 19 17:21:44 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WnfXT0vshz5T875; Mon, 19 Aug 2024 17:21:45 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WnfXT0bnYz4JZt; Mon, 19 Aug 2024 17:21:45 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724088105; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=TeKsaMddvdd9scABpN5qtmpMyG3yaqYhasArGQr7+oo=; b=XlC0BHIgpl1TJJLtjdx5lFpOEeyoF5XJX7TiH/EjYAG4KhU1ud7i7i4kqBNBJUWRdb7+4n 1es5LowwrZwrCdHfgl3ibQb+LQcF6ud6bb8PXUpa9pUH0kylB2pYfgPL88yv+F94uqAL+h MoPx2XgbWV/U7LgER2wogoDdCqH/Pc5ZvQdg0IxdTytXVabBu7KKZXmErAL5HPjPSLiwmK J3uK05rxCd+F64S4aTqJ1ntslnXRnOXDprR+r0CeTPIMWsAB6KQK+FMcYxQdSNy7/Zxo9z 56Z9uePD7CSEUxzduzIBPLDmb7gP8RlbCGqIqNDHglnjfmNiyCbckXJb6QRvHA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724088105; a=rsa-sha256; cv=none; b=leoOdLt/Or8tHf7jRRYOWEHlViNQTui3kOxMoPE1Ivx2UPggY8OTX0/L9tIRqCAF9+Ce9Q rDzQ6aZtSLKldn/rTF0ZkPNn1aOJfbAJFHiGpW6y3HGLdLbenxDMm9gpplobEiuWSVDmDa XLLftwFieQKcz5TS0L+stAvj/0VSEpvbqlpRGV9jiWlBt1UZ6+iU1bVmNNbUUcqlJ1Od93 HeuGipShfPC+9KNRbFK3mnMjb/sIkag9AaoAa9ujSHXEwYG6jG3x2mjkvYeHk46L83VETb etuFmG0xmbMaoUdOwnsfuOJ4EwzUGZ/7BV4uCE8S/w2+dt5IKwOyHayvKkWvSA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724088105; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=TeKsaMddvdd9scABpN5qtmpMyG3yaqYhasArGQr7+oo=; b=Ajj27nfnbTIgBLLN9wiXdD3ObYnhmcEVt9BWMJbBtItQgzFbhQOleNqyLK1BS32PG5nptJ 5OV8Y9xXLP6nusOf6r72e7vgign9VqVx6VWa0drITl0T1GN4CtJQYMMPPYVGptM27WsJbh cfFWH57oMSoWDJbducgo/u9avxF6Ka6tGxN5i69Ez28EjxKrBLNavZ19Tpd0TUJET4sFza omNZoiKteGZVOE17y2DmaqQtweBko7TOyQhS3rbd3mCEHGYdn2lfo1Y0C4pcyeumoIrGyd vOVoJbSywqprCkNthVZCAS+vhClNBNzZV/CFWu8d3E/hBkQ6fmMIWMTqC1k5Jg== Received: by freefall.freebsd.org (Postfix, from userid 1472) id E8C052EAB; Mon, 19 Aug 2024 17:21:44 +0000 (UTC) Date: Mon, 19 Aug 2024 17:21:44 +0000 From: Lorenzo Salvadore To: freebsd-hackers@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD Status Report - Second Quarter 2024 Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline; filename="report.txt" Content-Transfer-Encoding: 8bit FreeBSD Status Report Second Quarter 2024 Here is the second 2024 status report, with 20 entries. It has been very difficult to publish this status report within the usual schedule: indeed we are late. Unfortunately many of us have been busy with a lot of stuff, both inside and outside FreeBSD, thus some reports arrived late and report publication was slower than usual. Hopefully, this quarter was an exception and next quarter we will already be back on track, with 2024Q3 report published within October 2024. Have a nice read. Lorenzo Salvadore, on behalf of the Status Team. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2024-04-2024-06/ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection • Projects □ Audio Stack Improvements □ FreeBSD GitHub Pull Request Report • Userland □ Capsicum-rs □ Service jails — Automatic jailing of rc.d services • Kernel □ Hierarchical rate limits for OpenZFS □ A low-cost conditional execution mechanism • Architectures □ FreeBSD/riscv64 • Cloud □ FreeBSD on Microsoft HyperV and Azure □ OpenStack on FreeBSD • Documentation □ Documentation Engineering Team • Ports □ GCC on FreeBSD □ KDE on FreeBSD □ FreeBSD Erlang Ecosystem Ports update • Third Party Projects □ Containers and FreeBSD: Pot, Potluck and Potman ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. DevSummit 202405 The Core Team has presented the status update at the DevSummit 202405. Details are available at https://wiki.freebsd.org/DevSummit/202405 Passing of Mike Karels It is with a heavy heart that we have learned of Mike Karels' recent passing. We want to offer our sincere condolences to his family, friends, and the community for this loss. Mike was an inspirational fellow developer and will be sorely missed. In Memory of Mike Karels. For more details about him, please visit the FreeBSD Foundation’s page at: https://freebsdfoundation.org/mike_karels/ 2024 Core Team Election Core.12 appointed Muhammad Moinur Rahman (bofh@) and Allan Jude (allanjude@) as the managers of the 2024 Core Team election. After Allan decided to run for Core, Moin continued to handle all the election tasks independently. The result was announced on June 12th, with 8 members: • Allan Jude (allanjude@) • Dave Cottlehuber (dch@) • Gleb Smirnoff (glebius@) • Hiroki Sato (hrs@) • Li-Wen Hsu (lwhsu@) • Mathieu Arnold (mat@) • Olivier Cochard (olivier@) • Tobias C. Berner (tcberner@) Mike Karels has run for the 2024 Core Team election, and was in the top nine candidates in the result. After a discussion, core.13 came to the conclusion that the eight members will serve as the new team. Core.13 takes office on June 12th, and hold the handover meeting with core.12 on June 21st. The project thanks the outgoing core.12 members for their service in the last two years: • Baptiste Daroussin (bapt@) • Benedict Reuschling (bcr@) • Ed Maste (emaste@) • Greg Lehey (grog@) • John Baldwin (jhb@) • Emmanuel Vadot (manu@) • Mateusz Piotrowski (0mp@) Commit bits • Core approved the src commit bit for Osama Abboud (osamaabb@) • Core reactivated the src commit bit for Ryan Libby (rlibby@) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://freebsdfoundation.org/ Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://freebsdfoundation.org/journal/ Foundation Events URL: https://freebsdfoundation.org/our-work/events/ Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and worldwide community, and helping to advance the state of FreeBSD. We do this in both technical and non-technical ways. We are 100% supported by donations from individuals and corporations and those investments help us fund the: • Software development projects to implement features and functionality in FreeBSD • Sponsor and organize conferences and developer summits to provide collaborative opportunities and promote FreeBSD • Purchase and support of hardware to improve and maintain FreeBSD infrastructure • Resources to improve security, quality assurance, and continuous integration efforts • Materials and staff needed to promote, educate, and advocate for FreeBSD • Collaboration between commercial vendors and FreeBSD developers • Representation of the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity Last quarter we helped FreeBSD celebrate its 31st anniversary! This community sure loves to celebrate milestones like this one. We not only saw more users sharing their stories on social media, but many commercial users stepped in to promote their use cases and love for FreeBSD. It is exciting to see the growth of this project through the improvements made to FreeBSD, as well as the increase in users and contributors. Over the past few quarters, we have built up our technology, advocacy, and partnership teams to accelerate our work in improving the operating system, increasing the adoption and visibility of FreeBSD, and increasing the number of partners who help fund our work. Below you will find updates from each team to see the work we have accomplished to support you, the community and the operating system we all love. But, first I want to share a fundraising update. Last quarter we raised $41,154 towards our goal of raising over $2,000,000. You can see our 2024 budget to understand how we are spending your donations here: https://freebsdfoundation.org/wp-content/uploads/2024/03/Budget2024-Approved-Public.pdf. Over half the budget goes directly into improving and securing FreeBSD. If there is a security vulnerability out there, we have software developers on staff who can quickly step in, evaluate the situation, and put in a change or workaround if needed. We have a full-time developer who leads the continuous integration efforts and investigates ways to improve the tools to test code, improve test coverage, and help developers be more efficient. We have also allocated more funding towards our advocacy efforts. This includes creating content to highlight FreeBSD’s strengths and differentiators, talking to commercial users and documenting their use cases, and promoting the work you are doing. Please consider funding our efforts to help keep FreeBSD innovative, secure, and stable by making a donation here: https://freebsdfoundation.org/donate/. If you are a corporate user, please consider becoming a partner! Go here to find out more information about our partnership opportunities: https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/. OS Improvements During the second quarter of 2024, 204 src, 50 ports, and 11 doc tree commits identified The FreeBSD Foundation as a sponsor. The Foundation is sponsoring 13 projects. • Christos Margiolis continued to improve FreeBSD’s audio stack and provide audio developers with useful tools and frameworks to facilitate sound development on FreeBSD. Refer to the Audio Stack Improvements entry for details. • Pawel Dawidek is in the final stages of a project to add hierarchical rate limits to OpenZFS. For details, refer to the Hierarchical rate limits for OpenZFS report entry and the pull request in the OpenZFS repository. • Long-term contractor Olivier Certner was active in a few different parts of the tree: □ rtprio(2): Updating the number of queues per runqueue from 64 to 256 □ UnionFS: reviewed work from Jason A. Harmening. Jason’s work fixes many locking problems (wild accesses without locks, deadlocks, etc.), particularly in unionfs_rename() and improves locking logic. □ Vnode recycling/ZFS ARC reclaim: Reviewed a fix for bug #275594, liaised with upstream to obtain and test a backport, had an EN issued and applied as 13.3-RELEASE-p2, and started longer-term work to improve the vnode reclaiming mechanisms and have ZFS pass the right information □ ULE scheduler: Updated to work on a single runqueue instead of 3 for POSIX compliance with respect to the number of distinct SCHED_FIFO/ SCHED_RR priority levels □ Miscellaneous: Many (26) reviews, ports updates, and investigated DRM problems □ Published a EuroBSDCon 2023 conference report in the FreeBSD Journal. • Pierre Pronchery continued work on a security-focused project with the Foundation that included: □ working on a conversion tool from VuXML to OSV □ automating the generation of VuXML reports across all ports with security/osv-scanner □ running Coverity Scan reports around bhyve and assisting in rectifying the reported defects • Work continued on a joint project between Advanced Micro Devices (AMD) and The FreeBSD Foundation to develop a complete FreeBSD AMD IOMMU driver. This work will allow FreeBSD to fully support greater than 256 cores with features such as CPU mapping and will also include bhyve integration. Konstantin Belousov has been working on various parts of the project, including driver attachment, register definitions, an ACPI table parser, and utility functions. Two key components that need to be completed are context handling, which is mostly a generalization of Intel DMAR code, and page table creation. After this, the AMD driver’s enable bit can be turned on for testing. To follow all of Konstantin’s work, look for src commits tagged with Sponsored by fields for Advanced Micro Devices (AMD) and The FreeBSD Foundation. • The Vector Packet Processor (VPP) is an open-source, high-performance user space networking stack that provides fast packet processing suitable for software-defined networking and network function virtualization applications. Tom Jones is wrapping up his part on a project to port VPP to FreeBSD. The code has been shared with RG Nets, a co-sponsor of the work, for extensive testing. • Björn Zeeb continued to improve wireless networking on FreeBSD. As with last quarter, the focus was mainly on bug fixes and stability improvements. Most of Bjoern’s 30+ src commits were to LinuxKPI and net80211 code. • Philip Paeps is working on a 20-hour-per-month, six-month contract to continue modernizing the FreeBSD cluster. This work includes moving more servers to our newest cluster site at NYI in Chicago. • Moin Rahman is under two contracts. Moin is nearing completion of a Center for Internet Security (CIS) hardening guide and continues work to establish pre-commit CI. • Mina Galić continues efforts to put FreeBSD cloud-init support on par with Linux support. • Mitchell Horne presented his RISC-V work at the FreeBSD developer summit. You can read about the latest developments in the FreeBSD/riscv64 report entry. • Refer to Chih-Hsin Chang's OpenStack on FreeBSD report entry for the latest updates on the project to port OpenStack components so that OpenStack can be run on FreeBSD hosts. Other members of the Foundation’s technology team contributed to FreeBSD development efforts. For example, Mark Johnston, along with Andrew Turner, authored basic routines to build a Flattened Device Tree (FDT) for arm64 bhyve guests. The FDT describes various hardware components like CPUs, memory, UART, PCIe controller, interrupt controller, and platform timer, which the guest OS needs to know about. Ed Maste committed a variety of src contributions, including modernization of tzsetup(8) and correcting an issue with diff(1) options. Balancing their regular responsibilities, Li-Wen Hsu and Joe Mingrone contributed updates and fixes to various ports, including addressing pressing security issues. FreeBSD is participating in the 20th consecutive Google Summer of Code. The 11 projects for this summer are well underway. Continuous Integration and Workflow Improvement As part of our continued support of the FreeBSD Project, the Foundation supports a full-time staff member dedicated to improving the Project’s continuous integration system and test infrastructure. Partnerships and Research In the Second Quarter, Greg Wallace, the Foundation Partnerships lead, attended the Open Source Summit event in Seattle. There he joined Doug Rabson who gave a talk on the work of the FreeBSD OCI Runtime Extension working Group. You can check it out here. Greg also used the event to connect with a number of key tech companies to advance major joint technology initiatives. Greg’s write up on the event is here. Work continues on other highly-requested features. RG Nets and others have been making great strides to bring CUDA and related AI stack components to FreeBSD. The Foundation is seeking ways to coordinate across users of FreeBSD to get support for a variety of AI technologies on FreeBSD. One idea is to launch a FreeBSD AI lab that would pool money from supporters to get CUDA fully supported on FreeBSD and to round out DPU driver support. Please contact us if you would like to support such an initiative. Work continues to leverage the heroic work from the FreeBSD Community to get .NET supported on FreeBSD so that downstream dependencies can in turn better support FreeBSD. More to come on this front soon. Thanks to the generous grant from Alpha-Omega, the FreeBSD Foundation has undertaken two code audits of important subsystems carried out by Synactiv. Alpha-Omega is an open source project with a mission to protect society by catalyzing sustainable security improvements to the most critical open source software projects and ecosystems. Our most recent monthly update can be found here. The code audits will conclude in July and then we will then undertake a process audit and will also run a 2FA pilot. In Q1 and Q2, Greg participated in several meetings about various government regulations. In March, he represented FreeBSD at the CISA two-day Open Source Software (OSS) Security Summit alongside other Open Policy Alliance members. Previously, Greg collaborated with OPA to submit comments to CISA’s RFC on how the US Government can support the security and sustainability of Open Source. And in June, The FreeBSD Foundation joined the Open Regulatory Compliance Working Group at the Eclipse Foundation. This group aims to accelerate the development of cohesive cybersecurity processes required for regulatory compliance while offering a neutral environment for hosting technical discussions with the open source community at large. We are thrilled to welcome Alice Sowerby as a part time, contract Partnerships Program Manager. Alice is an experienced, multi-skilled leader, currently active in a number of open source domains. She is the co-host of the CHAOSS podcast and chair of the TODO group review team for the OSPO Book. Alice is providing program and project management for partnership initiatives, like Alpha-Omega, OCI FreeBSD Runtime Extension WG, and the Enterprise Working Group. Advocacy During the second quarter of 2024, we continued growing our efforts to drive awareness, advocate for the project, highlight users, and bring educational content to the FreeBSD community. Below are some of those efforts. • Organized the May 2024 FreeBSD Developer Summit, co-located with BSDCan. Check out both the videos and write ups from Summit. • Celebrated FreeBSD’s 31st Birthday with FreeBSD Week, which included many new user stories, and an interview with Beastie! • Released the Final Report from the 2024 FreeBSD Community Survey. • Announced the winners of the first annual Digital Security by Design (DSbD) Ecosystem Beacon Awards to celebrate innovators working with and enhancing CheriBSD. The Beacon awards are sponsored by the Foundation in partnership with Innovate UK and Digital Security by Design (DSbD). • Provided an overview of FreeBSD 14.1. • Updated the FreeBSD End User page with new interviews and a number of new case studies including ones from Netflix, Metify, and RGNets. • Published numerous blogs including: □ FreeBSD Foundation Delivers V1 of FreeBSD SSDF Attestation to Support Cybersecurity Compliance □ FreeBSD: The torchbearer of the original operating system distribution □ The 2024 FreeBSD Foundation Budget Journey: Choosing Where We Invest □ Why FreeBSD Continues to Innovate and Thrive □ Innovating the Future: Arm’s Strategic Embrace of FreeBSD □ Why FreeBSD Events are Important to Furthering the Development of FreeBSD • Participated in the following contributed articles, interviews and podcasts: □ CIO Influence interview with Deb Goodkin □ SustainOSS Podcast interview with Deb Goodkin Legal/FreeBSD IP The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise. Go to https://freebsdfoundation.org to find more about how we support FreeBSD and how we can help you! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Release Engineering Team Links: FreeBSD 14.1-RELEASE announcement URL: https://www.freebsd.org/releases/14.1R/announce/ FreeBSD 13.4-RELEASE schedule URL: https://www.freebsd.org/releases/13.4R/schedule/ FreeBSD releases URL: https://download.freebsd.org/releases/ISO-IMAGES/ FreeBSD development snapshots URL: https://download.freebsd.org/snapshots/ISO-IMAGES/ Contact: FreeBSD Release Engineering Team, The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. The Team mourns the loss of Mike Karels, who was the Deputy Release Engineering Lead and mere days before his death agreed to take the role of Release Engineer for 13.4-RELEASE. The Team managed 14.1-RELEASE, leading to the final RELEASE build and announcement in June. During the second quarter of the year, the Team has gained new members: Ed Maste (Deputy Release Engineer Lead), Dave Cottlehuber, John Hixson, Mahdi Mokhtari, Doug Rabson, Muhammad Moinur Rahman. Planning has started for the upcoming 13.4-RELEASE cycle. The Release Engineering Team continued providing weekly development snapshot builds for the main, stable/14, and stable/13 branches. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cluster Administration Team Links: Cluster Administration Team members URL: https://www.freebsd.org/administration/#t-clusteradm Contact: Cluster Administration Team FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronize its distributed work and communications. In this quarter, the team has worked on the following: • Regular support for FreeBSD.org user accounts. • Regular disk and parts support (and replacement) for all physical hosts and mirrors. • Cluster software refresh. • Moving cluster services to Chicago. Cluster software refresh Except for the package builders and developer-facing ("dogfood") machines, the FreeBSD cluster mostly tracks stable/X branches. This quarter, we started moving the stable/13 hosts to stable/14. At the time of this writing, there are 133 physical machines in the cluster, 48 run current, and 64 have been upgraded to stable/14. The remaining machines are slated for upgrading or decommissioning in the near future. Of the 290 jails in the cluster, 206 run stable/14. 12.x: Regular 2, Jails 8 13.x: Regular 19, Jails 68 14.x: Regular 64, Jails 206 >15.x: Regular 48, Jails 8 ----------------------------- Total: Regular 133, Jails 290 Total installations: 423 Running -RELEASE|{-p*}: 0 Total geographic sites: 16 Moving cluster services to Chicago Earlier this year, we started building up our new site in Chicago. This quarter, we began decommissioning older machines in New Jersey and moving services to the newer machines in Chicago. Our long-term goal is for Chicago to become our primary location. This work will take several more months to complete. FreeBSD Official Mirrors Overview Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Sweden, Taiwan, United Kingdom (full mirror site), United States of America — California, Chicago, New Jersey (primary site), and Washington. The hardware and network connection have been generously provided by: • Cloud and SDN Laboratory at BroadBand Tower, Inc • Department of Computer Science, National Yang Ming Chiao Tung University • Equinix • Internet Association of Australia • Internet Systems Consortium • INX-ZA • KDDI Web Communications Inc • Malaysian Research & Education Network • MetaPeer • New York Internet • NIC.br • Teleservice Skåne AB • Your.Org New official mirrors are always welcome. We have noted the benefits of hosting single mirrors at Internet Exchange Points globally, as evidenced by our existing mirrors in Australia, Brazil, and South Africa. If you are affiliated with or know of any organizations willing to sponsor a single mirror server, please contact us. We are particularly interested in locations on the United States West Coast and throughout Europe. See generic mirrored layout for full mirror site specs and tiny-mirror for a single mirror site. Sponsors: The FreeBSD Foundation and Netzkommune ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Continuous Integration Links: FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org FreeBSD CI Tinderbox view URL: https://https://tinderbox.freebsd.org FreeBSD CI artifact archive URL: https://artifact.ci.FreeBSD.org Hosted CI wiki URL: https://wiki.FreeBSD.org/HostedCI 3rd Party Software CI URL: https://wiki.FreeBSD.org/3rdPartySoftwareCI Tickets related to freebsd-testing@ URL: https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals FreeBSD CI Repository URL: https://github.com/freebsd/freebsd-ci dev-ci Mailing List URL: https://lists.FreeBSD.org/subscription/dev-ci Contact: Jenkins Admin Contact: Li-Wen Hsu Contact: freebsd-testing Mailing List Contact: IRC #freebsd-ci channel on EFNet In the second quarter of 2024, we worked with the project contributors and developers to address their testing requirements. Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD. Important completed tasks: • Added new hardware purchased by the FreeBSD Foundation in Chicago site to the CI cluster • Repurposed decommissioned pkg builder as build agent and added to the CI cluster • Adjusted the job dispatching mechanism based on the machine capability • bofh@ merged https://reviews.freebsd.org/D43786 as Add preliminary in-tree CI infrastructure for developers so they can replicate an environment or results similar to https://ci.FreeBSD.org • Decommission armv6 jobs for the main branch Work in progress tasks: • Merging Pre-commit CI with CIRRUS-CI • Designing and implementing pre-commit CI building and testing and pull/ merge-request based system (to support the workflow working group) • Proof of concept system is in progress. • Designing and implementing use of CI cluster to build release artifacts as release engineering does, starting with snapshot builds • Simplifying CI/test environment setting up for contributors and developers • Setting up the CI stage environment and putting the experimental jobs on it • Redesigning the hardware test lab and adding more hardware for testing Open or queued tasks: • Collecting and sorting CI tasks and ideas • Setting up public network access for the VM guest running tests • Implementing use of bare-metal hardware to run test suites • Adding drm ports building tests against -CURRENT • Planning to run ztest tests • Helping more software get FreeBSD support in its CI pipeline (Wiki pages: 3rdPartySoftwareCI, HostedCI) • Working with hosted CI providers to have better FreeBSD support Please see freebsd-testing@ related tickets for more WIP information, and do not hesitate to join the effort! Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Collection Links: About FreeBSD Ports URL:https://ports.FreeBSD.org Contributing to Ports URL: https://docs.freebsd.org/en/articles/contributing/#ports-contributing Ports Management Team URL: https://www.freebsd.org/portmgr/ Ports Tarball URL: http://ftp.freebsd.org/pub/FreeBSD/ports/ports/ Contact: Tobias C. Berner Contact: FreeBSD Ports Management Team The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. Below is what happened in the last quarter. According to INDEX, there are currently 32,471 ports in the Ports Collection. There are currently ~3,497 open ports PRs. The last quarter saw 10,525 commits by 160 committers on the main branch and 1771 commits by 107 committers on the 2024Q2 branch. Compared to last quarter, this means a large decrease in the number of commits on the main branch (down from 12,991) and backports to the quarterly branch (compared to 888). The number of ports also increased (up from 32,244). The most active committers to main were: • sunpoet 3739 • yuri 1450 • jbeich 491 • eduardo 220 • bofh 200 • diizzy 197 • rene 188 • fernape 156 • jhale 133 • arrowd 129 A lot has happened in the ports tree in the last three quarter, an excerpt of the major software upgrades is: • pkg 1.21.3 • Default version of lazarus switched to 3.4.0 • Default version of fpc switched to 3.2.3 • Default version of python switched to 3.11 • chromium updated from 123.0.6312.86 to 126.0.6478.126 • firefox updated from 124.0.1 to 127.0.2 • firefox-esr updated from 115.9.0 to 115.12.1 • rust updated from 1.77.0 to 1.79.0 • sdl2 updated from 2.6.3 to 2.8.2 • wlroots updated from 0.17.2 to 0.17.4 • wine updated from 8.0.2 to 9.0 • wine-devel updated from 9.4 to 9.11 • xorg-server updated from 21.1.11 to 21.1.13 • qt5 updated from 5.15.13 to 5.15.14 • qt6 updated from 6.6.3 to 6.7.2 • kf5 updated from 5.115.0 to 5.116.0 • kf6 updated from 6.0.0 to 6.3.0 • plasma6 updated from 6.0.2 to 6.1.1 During the last quarter, pkgmgr@ ran 24 exp-runs to test various ports upgrades, updates to default versions of ports, subpackage support and base system changes. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Projects Projects that span multiple categories, from the kernel and userspace to the Ports Collection or external projects. Audio Stack Improvements Contact: Christos Margiolis The FreeBSD audio stack is one of those fields that does not attract the same attention and development as others do, since it has been left largely unmaintained, and, although high in quality, there is still room for improvement — from lack of audio development frameworks, to missing userland utilities and kernel driver-related bugs. This project is meant to touch on all those areas, and as such, is more of a general improvement project, than an implementation of a specific feature. Important work since last report: • Asynchronous audio device detach is now possible. This functionality already ships with FreeBSD 14.1-RELEASE, as well as 14-STABLE. • Got rid of the "snd_clone" device cloning framework used in sound(4) and replaced it with DEVFS_CDEVPRIV(9). More info about behavior changes in the commit description. Also ships with 14.1-RELEASE and 14-STABLE. • Several sound(4) crash and bug fixes. • More out of the box support for snd_hda(4) laptop sound. • Series of commits that clean up and simplify parts of sound(4). • Several fixes regarding the OSS API, with the most notable so far being a proper implementation of the SNDCTL_AUDIOINFO and SNDCTL_ENGINEINFO IOCTLs. • Started implementing audio(3), an OSS audio and MIDI library. • Took over maintenance of virtual_oss(8). Future work includes: • Implementation of an audio(8) utility, in similar fashion to mixer(8). • Implementation of a bluetooth device management utility. • Improve mixer(3) and mixer(8). • Improve documentation and test suite where needed. • Attempt to find a better (ideally automatic) way to handle snd_hda(4) pin-patching. This is an experimental attempt and is not guaranteed to actually yield a working result. You can also follow the development process in freebsd-multimedia@, where I post regular reports. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD GitHub Pull Request Report Links: GitHub Working Group wiki page URL: https://wiki.freebsd.org/WorkingGroup/GitHub FreeBSD Base System Pull Requests URL: https://github.com/freebsd/freebsd-src/pulls Contact: Warner Losh The FreeBSD Project has been trying an experiment to accept contributions via GitHub pull requests. We have learned a lot in the last year that we’ve been doing this. We have created a number of rules relating to the pull requests. In general, pull requests should only be for things that are user-visible, add value to the project and are ready to go, modulo final review. Current status: • We are able to keep up with the pull requests doing everything by hand, but only if we do it at least weekly. • We have discovered the by-hand process is tedious and error-prone. • We can stage multiple pull requests in a testing branch so we can batch-up testing. • We can automatically land the result so merged pull requests show up as merged in GitHub infrastructure. We need help with automating the process: • Add automated testing that is context specific (for example, run igor over man pages). • Add build/install tests that test-boot the resulting image. • Automate common tasks, like man page corrections, into staging process. • Add simple smoke testing for the staging branch for tier 1 architectures. • Investigate optionally integrating Jenkins testing to scale up the size of changes we can accept. • Integrate with Bugzilla problem reports and Phabricator reviews. • Improve the submitter experience on GitHub by automating common feedback to mistakes in the pull requests. • Create checklists for submitters to reduce errors. • Create better reporting about pull requests, especially the frequent contributors of good pull requests. We are coordinating on FreeBSD’s Discord in the #github-hacking channel. Join us there to pitch in, or just chat about the project. Once things are fine-tuned, we want to publicity to steer contributors, at least the base system, to GitHub pull requests. We need more developers looking at the FreeBSD GitHub pull requests. We will also need more developers to review and land pull requests once it is automated and the automation has matured. We sincerely hope that we can improve the FreeBSD contribution experience with this, as well as gain useful fixes from the community. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Userland Changes affecting the base system and programs in it. Capsicum-rs Links: capsicum-rs on GitHub URL: https://github.com/dlrobertson/capsicum-rs capsicum-net on GitHub URL: https://github.com/asomers/capsicum-net Contact: Alan Somers Capsicum is a lightweight OS capability and sandbox framework implementing a hybrid capability system model. I have adopted the library providing Rust bindings for Capsicum, and extended it with support for libcasper(3) and cap_net(3). It is already being used by net-mgmt/nfs-exporter and by a TLS-enabled FTP server (the FTP server is closed-source, but all of the interesting bits reside in an open source library, and an example server can be found at https://github.com/bolcom/libunftp/tree/master/crates/unftp-sbe-fs/examples). Sponsor: Axcient ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Service jails — Automatic jailing of rc.d services Links: rc-article part for Service Jails URL: https://docs.freebsd.org/en/articles/rc-scripting/#rcng-service-jails Contact: Alexander Leidinger Service jails extend the rc(8) system to allow automatic jailing of rc.d services. A service jail inherits the filesystem of the parent host or jail, but uses all other limits of the jail (process visibility, restricted network access, filesystem mounting permissions, sysvipc, …​) by default. Additional configuration allows inheritance of the IPs of the parent, sysvipc, memory page locking, and use of the bhyve virtual machine monitor (vmm(4)). The base system infrastructure and the basesystem rc.d services are committed to 15-current, and the handbook / rc article updates are committed to the documentation. Next steps are to extend services in the ports collection to be able to make use of it. If you want to put e.g. nginx into a service jail and allow IPv4 and IPv6 access, simply change rc.conf(5) to have: nginx_svcj_options=net_basic nginx_svcj=YES While this does not have the same security benefits as a manual jail setup with a separate filesystem and IP/VNET, it is much easier to set up, while providing some of the security benefits of a jail like hiding other processes of the same user. Any testing and feedback (even as simple as "service X works in a service jail") is welcome. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Kernel Updates to kernel subsystems/features, driver support, filesystems, and more. Hierarchical rate limits for OpenZFS Links: Pull request URL: https://github.com/openzfs/zfs/pull/16205 Contact: Pawel Dawidek Rate limits allow to limit bandwidth and number of metadata operations per dataset. Hierarchical rate limits allow for granular resource control especially in shared environments, eg. when a single ZFS pool serves data to multiple, independent virtual machines or jails. Because the limits are hierarchical, they are enforced like the quota property: the children datasets must obey the limits of the parent dataset. The limits can be configured using six new properties: limit_bw_read, limit_bw_write, limit_bw_total, limit_op_read, limit_op_write, limit_op_total The limit_bw_* properties limit the read, write, or combined bandwidth, respectively, that a dataset and its descendants can consume. Those limits are in bytes per second. The limit_op_* properties limit the read, write, or both metadata operations, respectively, that a dataset and its descendants can generate. Those limits are in number of operations per second. Limits are applied to file systems and ZFS volumes (and their snapshots). The initial work is done and the pull request is up for review. Sponsor: Klara Systems Sponsor: FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ A low-cost conditional execution mechanism Links: FreeBSD wiki URL: https://wiki.freebsd.org/SummerOfCode2024Projects/ZeroCostConditionalExecutionMechanism Contact: Marko Vlaić Contact: Bojan Novković (mentor) < bnovkov@freebsd.org> This project aims to implement a low-cost conditional execution mechanism, similar to the static_key interface in Linux. The current working name is zcond, as in zero-cost conditional. The idea is to reduce the overhead of rarely used features in performance sensitive kernel code paths. Specifically, code blocks of the following, simple structure, are targeted: if(some_global_flag == true) { do_some_additional_task(); } A block like this can cause performance overhead in a frequently executed piece of code. The motivating use case for the mechanism is tracing (as outlined here in the wiki), but the project will identify more areas where this mechanism could be applied. The backbone of the mechanism is runtime instruction hot patching, making it highly architecture dependent. Great care has to be given to security, because kernel instructions are overwritten at runtime. More details and some implementation ideas can be found in the project proposal on the project wiki page. More documents describing the implementation and design decisions will be produced, as the project moves along. The goal of the project is to produce a working implementation of the mechanism for the x86-64 architecture. It will then be applied to an existing piece of kernel code and benchmarked. If the benchmark results come out positive, it will be ported to other architectures. This project is a part of the Google Summer of Code 2024.. The project is still in its early stages, but any feedback would be highly appreciated. Help wanted • General feedback on the mechanism, API and implementation • More use cases besides tracing are welcome • Code review • Name suggestions Sponsor: Google LLC (GSoC 2024) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Architectures Updating platform-specific features and bringing in support for new hardware platforms. FreeBSD/riscv64 Links: Wiki Homepage URL: https://wiki.freebsd.org/riscv Contact: Mitchell Horne Contact: Ruslan Bukin Contact: Jari Sihvola The FreeBSD/RISC-V project is providing support for running FreeBSD on the RISC-V Instruction Set Architecture. BSDCan Devsummit Updates Mitchell gave a presentation on the status of the FreeBSD/riscv64 platform at the June developers' summit, part of BSDCan 2024. The presentation discussed the challenges of supporting the evolving RISC-V ISA, and gave a brief overview of some available hardware targets. It is informal in nature, but available to watch on youtube. https://www.youtube.com/watch?v=O7zW7Z9U0ns StarFive JH7110 SoC / VisionFive v2 Work has been ongoing to support the JH7110 RISC-V SoC in FreeBSD. This SoC is present in several existing RISC-V SBCs. The primary support target is the VisionFive v2, but this work is likely to benefit similar hardware such as the Pine64 Star64 and the Milk-V Mars. At present, the support in CURRENT is partially complete. What is working: * UART * clk/reset drivers * MMC/SD The next target is working ethernet, which is supported with extensions to the if_eqos driver. This code is functional, but still in review. Work on this has been performed by Jari, with review, testing, and integration from Mitchell. https://wiki.freebsd.org/riscv/StarFive T-HEAD/XuanTie CPU Support As discussed in the devsummit presentation, these CPUs present several barriers to support. The problems come primarily from custom vendor extensions: non-coherent device I/O with custom cache management instructions, and a custom (spec-violating) implementation of page-based memory types. Combined, these quirks require difficult and invasive changes to pmap, busdma, and early boot code. At the same time, we are seeing an increasing amount of available hardware based on this IP, and so support becomes a repeated question and incentive. Work on page-based memory types is underway and expected to land soon in CURRENT. This feature allows individual virtual memory pages to be assigned specific properties, e.g. cacheability requirements. The riscv64 pmap has been extended to support the official RISC-V 'Svpbmt' extension, and the T-HEAD version of PBMT. These alternative encodings are incompatible, but provide similar functionality. Work on the device coherence and cache management challenges will begin next quarter. The hope is that this foundational work will (eventually) enable board support for available RISC-V hardware such as: * Allwinner D1 (Nehza) * Sipeed Lichee Pi 4A * Beagle-V Ahead * Milk-V Pioneer RISC-V Hypervisor Experimental support for the RISC-V hypervisor in bhyve/vmm(4) is under active development. Currently, single-core VMs are possible, and the guest can boot to multi-user. Note: the "H" (hypervisor) extension is not implemented by any known existing or upcoming RISC-V hardware. It is fully supported by software simulators such as Spike or QEMU. https://wiki.freebsd.org/riscv/bhyve Sponsor: The FreeBSD Foundation (mhorne’s work) Sponsor: UKRI (br’s work) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cloud Updating cloud-specific features and bringing in support for new cloud platforms. FreeBSD on Microsoft HyperV and Azure Links: Microsoft Azure article on FreeBSD wiki URL: https://wiki.freebsd.org/MicrosoftAzure Microsoft HyperV article on FreeBSD wiki URL: https://wiki.freebsd.org/HyperV Contact: Microsoft FreeBSD Integration Services Team Contact: freebsd-cloud Mailing List Contact: The FreeBSD Azure Release Engineering Team Contact: Wei Hu Contact: Souradeep Chakrabarti Contact: Li-Wen Hsu In this quarter, we have published the 14.1-RELEASE on Azure Marketplace. Souradeep Chakrabarti from Microsoft has improved the TLB flushing mechanism in Azure. Work in progress tasks: • Automating the image building and publishing process and merging to src/ release/. • Building and publishing snapshot builds to Azure community gallery. • Testing adding FreeBSD support in Azure Pipelines □ https://github.com/microsoft/azure-pipelines-agent/pull/3266 The above tasks are sponsored by The FreeBSD Foundation, with resources provided by Microsoft. Open tasks: • Update FreeBSD-related doc at Microsoft Learn • Update sysutils/azure-agent to the latest version • Upstream local modifications of Azure agent • Port Linux Virtual Machine Extensions for Azure Sponsor: Microsoft for people in Microsoft, and for resources for the rest Sponsor: The FreeBSD Foundation for everything else ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ OpenStack on FreeBSD Links: OpenStack URL: https://www.openstack.org/ OpenStack on FreeBSD URL: https://github.com/openstack-on-freebsd Contact: Chih-Hsin Chang Contact: Li-Wen Hsu The OpenStack on FreeBSD project aims to integrate OpenStack cloud infrastructure with the FreeBSD operating system, utilizing FreeBSD’s unique features while maintaining compatibility with OpenStack standards. In the second quarter of 2024, we continued to advance the project significantly. One of our key activities was attending BSDCan 2024, where we presented on "Towards a Robust FreeBSD-based Cloud: Porting OpenStack Components". This presentation helped increase the project’s visibility and attracted interest from potential contributors. We expanded the current single-node proof-of-concept (POC) site to a three-node setup. This involved detailed environment setup and network planning. Additionally, we began migrating the base to FreeBSD 15.0-CURRENT to ensure our project stays aligned with the latest advancements in FreeBSD. We also started working on adapting the manual installation steps and code patches into FreeBSD ports, aiming to streamline the installation process for future users. Another major milestone was initiating work on making bare-metal provisioning function on both FreeBSD instances and service hosts for OpenStack Ironic. Looking forward to the next quarter, our focus will be on refining these advancements and further enhancing the project’s robustness and ease of use. Specifically, we aim to upgrade our OpenStack components from the Xena version to a more recent release, as Xena has entered the "unmaintained" phase and will soon reach EOL. We welcome any suggestions and contributions from the community to help us achieve our goals. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Documentation Noteworthy changes in the documentation tree, manual pages, or new external books/documents. Documentation Engineering Team Link: FreeBSD Documentation Project URL: https://www.freebsd.org/docproj/url Link: FreeBSD Documentation Project Primer for New Contributors URL: https://docs.freebsd.org/en/books/fdp-primer/url Link: Documentation Engineering Team URL: https://www.freebsd.org/administration/#t-docengurl Contact: FreeBSD Doceng Team The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see FreeBSD Doceng Team Charter. Document changes During this quarter multiple pieces of the documentation were updated including the removal of mentions to ports that were removed from the ports tree, typos, URL corrections, and asciidoc improvements. These are three highlighted contributions in this quarter: • Best practices related to vendor import were documented. URL: https://cgit.freebsd.org/doc/commit/?id=fe494e72df138266f6da2b9170cf0215275a6aaf • A section about service jails was added to the handbook. URL: https://cgit.freebsd.org/doc/commit/?id=8f4754a9a6ee8f2503cfb68d14afa99b17729e7f • bhyve documentation was improved. URL: https://cgit.freebsd.org/doc/commit/?id=68cbd16c4e7c199cfdfb2b54110ad1470b4d7a2e FreeBSD Translations on Weblate Link: Translate FreeBSD on Weblate URL: https://wiki.freebsd.org/Doc/Translation/Weblateurl Link: FreeBSD Weblate Instance URL: https://translate-dev.freebsd.org/url Q2 2024 Status • 17 team languages • 214 registered users 9 new translators joined Weblate: • BFR (de_DE) • Elwood (de_DE) • Freebsd-Freund (de_DE) • MSantos (pt) • SINF-KEN (fr_FR, nl_NL) • aperechnev (ru) • edsonwolf • fdecunta (es_ES) • wheatfox (zh_CN, zh_HANS) Languages • Chinese (Simplified) (zh-cn) (progress: 7%) • Chinese (Traditional) (zh-tw) (progress: 3%) • Dutch (nl) (progress: 1%) • French (fr) (progress: 1%) • German (de) (progress: 1%) • Greek (el) (progress: 1%) • Indonesian (id) (progress: 1%) • Italian (it) (progress: 5%) • Korean (ko) (progress: 32%) • Norwegian (nb-no) (progress: 1%) • Persian (fa-ir) (progress: 3%) • Polish (progress: 2%) • Portuguese (progress: 0%) • Portuguese (pt-br) (progress: 22%) • Spanish (es) (progress: 36%) • Turkish (tr) (progress: 2%) We want to thank everyone that contributed, translating or reviewing documents. And please, help promote this effort on your local user group, we always need more volunteers. Packages maintained by DocEng During this quarter the following work was done in packages maintained by doceng@: • textproc/docproj-legacy: Fix build with DBLATEX • textproc/docproj-legacy: Fix poudriere warning • textproc/rubygem-asciidoctor-epub3: Add missing run dependency • www/gohugo: Update to 0.125.4 Open issues There are 3 Open PRs in bugzilla assigned to doceng@: • 279815 status reports: ERR_TOO_MANY_REDIRECTS • 276923 www/gohugo link error under poudriere • 267274 Please remove the zh-CN Handbook of the current FreeBSD website During this quarter doceng@ closed 3 PRs: • 278904 misc/freebsd-doc-en: HTML should be single page • 278732 www/gohugo: Update to v125.5 • 278504 textproc/rubygem-asciidoctor-epub3: A run-time dependency is missing for rubygem-asciidoctor-epub3 port ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves. GCC on FreeBSD Links: GCC Project URL: https://gcc.gnu.org/ GCC 11 release series URL: https://gcc.gnu.org/gcc-11/ GCC 12 release series URL: https://gcc.gnu.org/gcc-12/ GCC 13 release series URL: https://gcc.gnu.org/gcc-13/ GCC 14 release series URL: https://gcc.gnu.org/gcc-14/ Contact: Lorenzo Salvadore Upstream has released GCC 14.1. Therefore port lang/gcc-14 has been created, as well as lang/gcc15-devel which tracks the new latest development GCC version. Previous major versions of GCC are being updated as well. Only very little work has been done on existing bugs for GCC ports this quarter, contrary to the original plan stated in the precedent report. This is due to the fact that I noticed an increasing interest in upstream to support GCC on FreeBSD, which however gets blocked by the fact that GCC sources do not build out-of-the-box on our platform, but needs instead many patches which are in our ports tree framework. It is then necessary to focus on upstreaming all of those patches, possibly at once and not one at the time as it has been done until now, and to also regularly run the tests suite, fixing all tests that fail. Then I am working on a new setup of automation that allows me to build and test all supported GCC versions as efficiently as possible, including GCC from sources but without the ports tree framework support. All of this has significantly slowed down usual GCC ports maintainership (users of the -devel ports have probably noticed that they are being updated much less frequently), but I am confident that it will eventually pay off. It should also be noted that Robert Clausecker has enabled lang/gcc11, lang/ gcc12, and lang/gcc13 for riscv64 architecture as the ports build fine on 15-CURRENT. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ KDE on FreeBSD Links: KDE/FreeBSD initiative URL: https://freebsd.kde.org/ FreeBSD — KDE Community Wiki URL: https://community.kde.org/FreeBSD Contact: Adriaan de Groot The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree. The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. The KDE team is part of desktop@, building the software stack to make FreeBSD beautiful and usable as a daily driver graphical desktop workstation. We missed a quarter, while the broader KDE community celebrated the KDE Megarelease of KDE Frameworks 6, KDE Plasma 6 and KDE Gear. The latest software is still not available on FreeBSD, pending more testing and some integration work. Infrastructure CMake was updated several times and is now version 3.29.6, the latest upstream release. CMake in the ports framework now supports setting parallel-build for tests. Qt5 is now on long-term support and updates only rarely. An update to 5.15.14 and WebEngine to 5.15.17 was landed in May. Qt6 and the Python bindings for Qt, Pyside, were updated to version 6.7.2. KDE Stack KDE Gear, Plasma and Frameworks release happen very regularly. These updates arrive in the FreeBSD ports tree only piecemeal, due to lagging work on compatibility and testing. • KDE Frameworks reached version 6.3.0 • KDE Plasma 6 Desktop was updated to version 6.0.4 • KDE Gear 6 has not yet arrived in the ports tree Related Ports The KDE ecosystem includes a wide range of ports — most maintained by kde@, all building on a shared base of Qt and KDE Frameworks. The KDE team updates them all as needed. This quarter the KDE team would like to thank Tobias C. Berner, Gleb Popov and Jason E. Hale again for keeping things up-to-date. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Erlang Ecosystem Ports update Links: FreeBSD Erlang wiki URL: https://wiki.freebsd.org/Erlang Erlang/OTP language URL: https://erlang.org/ Elixir language URL: https://elixir-lang.org/ Gleam language URL: https://gleam.run/ Contact: FreeBSD Erlang mailing list The Erlang runtime system, commonly known as the BEAM, provides a runtime that is used by a number of programming languages and applications in the FreeBSD ports collection. Notable changes in 2024 include: • adding OTP27, the latest Erlang runtime release, Elixir 1.17, and Gleam 1.20 • more than 57 point release updates so far in 2024 • improved inline documentation within Erlang ports • moved RabbitMQ port to the generic UNIX build, decoupling this from Elixir as a build-time dependency. This enables moving RabbitMQ to the latest supported release. Users of RabbitMQ need to update each quarter to avoid being stuck on an unsupported release of Erlang/OTP + RabbitMQ Note that as the upstream Erlang OTP team only commit to supporting the two latest major releases, more and more point updates are arriving for OTP26-27, but not for the older Erlang runtime releases, which are now unlikely to get security and bug fixes. During 2024Q3, the Erlang team is planning to: • migrate the base lang/erlang port to OTP26 and update related dependencies Additional testing and community contributions are welcome, please reach out on the mailing list, especially if you are able to help testing of specific port updates. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Third Party Projects Many projects build upon FreeBSD or incorporate components of FreeBSD into their project. As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions. Containers and FreeBSD: Pot, Potluck and Potman Links: Pot organization on GitHub URL: https://github.com/bsdpot Contact: Luca Pizzamiglio (Pot) Contact: Bretton Vine (Potluck) Contact: Michael Gmelin (Potman) Pot is a jail management tool that also supports orchestration through Nomad. Potluck aims to be to FreeBSD and Pot what Dockerhub is to Linux and Docker: a repository of Pot flavours and complete container images for usage with Pot and in many cases Nomad. During this quarter, there were no new Pot releases. Potluck images saw some updates again though. All images have been rebuilt for the new quarterly packages, a new Opensearch container has been added. Additional features, updates and fixes have been committed to containers like PostgreSQL-Patroni or Nomad-Server-TLS. In total, there are 58 container images and templates available now. As always, feedback and patches are welcome. Sponsors: Nikulipe UAB, Honeyguide Group From nobody Mon Aug 19 19:07:14 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wnlnh3TXSz5TX8n for ; Mon, 19 Aug 2024 21:18:32 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wnlng4Vhvz4qCL for ; Mon, 19 Aug 2024 21:18:31 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=sdaoden.eu header.s=citron header.b=D1+2Oo+B; dkim=pass header.d=sdaoden.eu header.s=orange header.b=LDpw3obn; dmarc=none; spf=pass (mx1.freebsd.org: domain of steffen@sdaoden.eu designates 217.144.132.164 as permitted sender) smtp.mailfrom=steffen@sdaoden.eu DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=citron; t=1724102302; x=1724768968; h=date:author:from:to:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: author:from:subject:date:to:cc:resent-author:resent-date:resent-from: resent-sender:resent-to:resent-cc:resent-reply-to:resent-message-id: in-reply-to:references:mime-version:content-type: content-transfer-encoding:content-disposition:content-id: content-description:message-id:mail-followup-to:openpgp:blahblahblah; bh=L/+n21zXyP1vpT/pjpz+1dPj23Atz8tzERWUDUtKhNU=; b=D1+2Oo+BFmXTrl/3nYujDsDcu96lAXrljIuEjkAB5ahNyrMuFc/8QWnuS/Ti2GkKp4mkKgU4 7juRHyEmgngoBUJMOYa8y/m+KLw2jUzHkiW23Fdgo2d26y7f6cqoZtVrIYgQbIoC2D8tGybF0i Wz+iiTvbUvClyNvxlki1od836I2m7Kh8yW5tNwx1qXhDYsRWCQcQnu9gzfxdIWoMfgao42Qo0G guDhy28pEoHPITmGZsRNagXREa9PzVOPTetw8c6p/boPqgK+sLoVTHWmKCzda5DwSccrh9oYn+ TbRHCzK364uYhK9umKmbWWV7V8xq+f+2Ai6iAFBolYiA1lQg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=orange; t=1724102302; x=1724768968; h=date:author:from:to:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: author:from:subject:date:to:cc:resent-author:resent-date:resent-from: resent-sender:resent-to:resent-cc:resent-reply-to:resent-message-id: in-reply-to:references:mime-version:content-type: content-transfer-encoding:content-disposition:content-id: content-description:message-id:mail-followup-to:openpgp:blahblahblah; bh=L/+n21zXyP1vpT/pjpz+1dPj23Atz8tzERWUDUtKhNU=; b=LDpw3obn7ngWR8rfSKSi4T2CKNtx56MCYkb0r/BBCCDjPSefhPXT7KFb3OwzPeI2VJ4Xyzs3 nWu8zcTIyT7TBQ== Date: Mon, 19 Aug 2024 21:07:14 +0200 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: freebsd-current@freebsd.org Subject: Re: a zfs thank you :) Message-ID: <20240819190714.mtYVCmQC@steffen%sdaoden.eu> In-Reply-To: References: Mail-Followup-To: freebsd-current@freebsd.org User-Agent: s-nail v14.9.25-599-g5c75a327b2 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.48 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.979]; R_DKIM_ALLOW(-0.20)[sdaoden.eu:s=citron,sdaoden.eu:s=orange]; R_SPF_ALLOW(-0.20)[+a]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15987, ipnet:217.144.128.0/20, country:DE]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[sdaoden.eu]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[sdaoden.eu:+] X-Rspamd-Queue-Id: 4Wnlng4Vhvz4qCL List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Jan Bramkamp wrote in : |On 31.07.24 17:02, void wrote: |> I was pleasantly surprised when I installed a new [1] zfs-on-root |> -current |> to rpi4 that when adduser was invoked, I was given the option to |> encrypt the homedir. This is a great feature for my context [2]. |> |> It doesn't automount on boot but I think this is more of a feature |> rather than a bug. One can have a different password to the GELI one used |> to boot up the whole system. |> |> I have not tested yet whether one can have the user, once logged in, |> mount |> their homedir with doas(1). Right now, I mount the homedir like so: |> |> zfs load-key -a (prompts for password) |> zfs mount -a |> |> as root. |> |> I could I guess make a doas line for the user for zfs load-key -r |> zfsfile/system. |> Can anyone suggest any better ideas please? |There is the pam_zfs_key.so PAM session module that should do exactly |what you're looking for if your users login with a password. It should |similar to the pam_ssh.so module if you're already familiar with that |one. Unless users provide the password there isn't much file system or |disk encryption can do for you against hardware theft since the |Raspberry Pi doesn't have any secure key storage nor would the kernel be |able to know when it has been stolen and stop auto-loading the keys. To suggest a screen locker for "warm" security. Ie here this is (on Linux, in /root/bin/zzz.sh upon lid close etc) if command -v X >/dev/null 2>&1 && command -v slock >/dev/null 2>&1; then had_z= for p in $(pgrep X); do uid=$(awk '/^Uid:/{print $2}' < /proc/$p/status) disp=$(sed -Ee 's/^.*DISPLAY=:([[:digit:]]+).*$/\1/' < /proc/$p/environ) [ -z "$disp" ] && disp=$(xargs -0 printf '%s\n' < /proc/$p/cmdline | awk '/^:[[:digit:]]+/{sub(":", ""); print}') if [ -z "$disp" ]; then [ -n "$had_z" ] && continue had_z=y disp=0 elif [ $disp = 0 ]; then [ -n "$had_z" ] && continue had_z=y fi act "DISPLAY=:$disp $SUPER -u $uid slock /dev/null 2>&1 &" done fi Unfortunately there is no other easy way i know to lock all X sessions otherwise. This is the problem i have with "encrypted home directories" per se, i do not use that, but have several encfs directories, like, say, ~/.sec.arena, which i mount via fuse as a normal user, and $HOME is nothing but a symlink farm like .xinitrc -> sec.arena/configs.git/home/.xinitrc so before i mount this that is all hollow. The zzz.sh script also does (simplified) if command -v encfs >/dev/null 2>&1; then grep encfs /proc/mounts | cut -d ' ' -f 2 | { while read line; do act "{ sync $line/.; umount $line; } /dev/null 2>&1 &" done } fi so that all these are unmounted upon LID close etc. (Unless some process uses any directory within as CWD/pwd(1), then not. Force unmounting does not work.) Ie that is all pretty uncomfortable (it is even more complicated in practice), but like this data i care of a bit more is not mounted when the LID is opened. (And data i really need to take care off is never mounted all the time. And "of course" the hard disk partition as such is also "cold" encrypted.) Ie, i just feel better that way. If you steal the laptop you can switch to another console, and, i mean, here is no automounter for USB sticks or what, no code runs then (i hope), but i do not know, but anyway, if all that time an encrypted home directory of myself would be unencrypted, that feels a bit odd. Anyhow. To remark that PAM sessions can easily be bypassed by any shell script (script /dev/null 2>&1 &), and, i looked at the ZFS PAM module in particular a few years ago, it did not do anything REAPER-alike by then. That is "script" may be running when the ZFS user logs out, and the PAM module will then likely unmount the ZFS home directory. One should at least hear about this situation once. It would be cool if the PAM implementations i know (Open and Linux) would consider adding a dedicated session reaper, with all session related modules stopping doing lots of dances, but instead relying on some generic PAM library support mechanism. Sounds a bit like a sophisticated and relevant Google Summer of Code or something project. --End of --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Tue Aug 20 02:14:58 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WntMs4Bqtz5V1PS for ; Tue, 20 Aug 2024 02:15:05 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WntMs3fqWz43pR for ; Tue, 20 Aug 2024 02:15:05 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724120105; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=qnMoADM1+QtAW852YHB2ZkMxWebWXtKnbYa6ltaG4Zs=; b=haQ3PVdj1Tw7SZFenigaZ0qeNHk7k/oO4l1UHF1ZZzofEZzZ8/PX8J1wA0KMte1sm79xdD TlyDpBHOd3dVD7gbkJK4tySuIJ/wMt0NfZYKbnDHI8ja54PSQuZrprqT3GaPCE06n9IjIV CBEnX6S0Q99kGqoZzCD0JgEQgu5SFoG761Lh3gPkeoi5Llzq/krI9QAruOwAS5XsH7nggD y1hG6jS23whrDw9vU4ldJb3OSdUmuDBt2N1uleCE3dPdxwxfo0dlQsNlLjr63TvdvAMVwV sWe+KjbodN0mVEfXD64DHeo0SndSUYbttFD66oVtHOSde8qIgoOLzqX69Psjnw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724120105; a=rsa-sha256; cv=none; b=idlcj8+ZuGdEu0H7+XAO2KxG0qmKSsUFw0OoriKWQV1MpB+5NRtCpXBSOwsY6mvP4MM+2I 1TyPuKRPZneDXVRwAK9FJ/ddiyFUn4+nx2ZDEAmrswXY7Nor7KzM/s3OhT+U3v2uCkW0tD V7qFE/Re/VhkvA6BeskyuM6h2gS6V77SpeOcQi3B2heCN9V5Oeqikz9Qdu9OUKy3E9g4hv r6TG89RUHUOOm5qbr2fcfumNdIfXITtD2B+dmob0lRD/IP+GuYv6s8oaplt24ZdDGmD1lY mPfEzRWFfJfQyKf3h1wfxSnjgE9BDnh69jCwu4GJ+T4r892uS68oLv4NXi/aJw== ARC-Authentication-Results: i=1; thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724120105; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: dkim-signature; bh=qnMoADM1+QtAW852YHB2ZkMxWebWXtKnbYa6ltaG4Zs=; b=J/C5/zqmrhbUj3RSEtO6TiVifG43yYEEZ3CeB5EVp//SgQ84tkFsGcNXvz7+68TasJ6QyK WEY7Omf7IehNirQ0N1FKKEaqdzIWN54dwAkgRyKL6kD8EqQPkqQsVNe+NpA23aM/Dq2F2w NBl/r2VM/v5k98zEcIt5rpSnr0ojlCHFRbrgTps+10YLk4zt1ngY27+q7sn8mhrAHy93Lt 8JF409zjAd35jJrFbss2R9U22rAy/nygz7jdNbmJsdmdA7qmEhgKDk18D1nJEkaKL6lOLR 5AMYtN4cSyQXNh1hSrG4qBtsDAKS+7wU7TgRVWa162w0E42VOkT38xzOCY01aA== Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.lerctr.org", Issuer "R10" (verified OK)) (Authenticated sender: ler/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4WntMs37M8z13lX for ; Tue, 20 Aug 2024 02:15:05 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=ler2019; h=Content-Type:Message-ID:Subject:To:From:Date:MIME-Version:Sender :Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description; bh=qnMoADM1+QtAW852YHB2ZkMxWebWXtKnbYa6ltaG4Zs=; b=PFMG3JCAPJeexDFLZZ0NiNZGMw cJWK4sksyiDT00psVez42DOto7+21puGNKOfj/PgCNgnLRKiqoc7LS06zMQtyZlLuBli4VEKIkGb6 eoB+899vAalIecNwouI2y8L/z1ziA2bSneppH5ZNIIvCUQUyl6C3CJ+k1Ra939v5YMxoXyYomyxvp eTshgZLh6wYkCcya/V5Orq0MS26JruISobgORXKaGNlfEcD9iSP6M4U4zH4boOagj+LcqyAL+HSIy 1pII2t57zTmDTI84CU8jF5nTtBLnNGhzN1PRdQwc5IAU4K+JFWfQNwrJ6eNJ2J9hqjDgEILnHeP8Z Sq2B6vCw==; Authentication-Results: thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none Received-SPF: softfail (thebighonker.lerctr.org: transitioning domain of FreeBSD.org does not designate 192.147.25.65 as permitted sender) client-ip=192.147.25.65; envelope-from=ler@FreeBSD.org; helo=webmail.lerctr.org; Received: from thebighonker.lerctr.org ([192.147.25.65]:11585 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.98 (FreeBSD)) (envelope-from ) id 1sgEKW-00000000OAe-42He for freebsd-current@freebsd.org; Mon, 19 Aug 2024 21:15:01 -0500 Received: from syn-070-123-041-087.res.spectrum.com ([70.123.41.87]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Mon, 19 Aug 2024 21:14:58 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Date: Mon, 19 Aug 2024 21:14:58 -0500 From: Larry Rosenman To: Freebsd current Subject: RTL8125: wont stay up Message-ID: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> X-Sender: ler@FreeBSD.org Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_ff964d91c30bb1634691318312b877ef"; micalg=pgp-sha256 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_ff964d91c30bb1634691318312b877ef Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed shows up, doesn't ping -- ifconfig up brings it back for ~4 packets ifconfig_re0="DHCP" ifconfig_re0_ipv6="inet6 accept_rtadv" ipv6_activate_all_interfaces="AUTO" rtsold_enable="YES" 15-CURRENT as of just now, port of net/realtek-re-kmod as of now as well. Ideas???? -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 --=_ff964d91c30bb1634691318312b877ef Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=488 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEHjgknedhWzvJgwVzaXyZsatIp30FAmbD/CUACgkQaXyZsatI p33rRwgAlYqBVwH/75ZXWBQWCjGeqNPIpOZCo3ZF1WmaD+3vRXKNyTZzN/5SRy4V GgnKYy32KbUCsaWAtaCuslOrE+9Kdj+BJkcbAFobDG76MgFCNwTSE1QhUfIJOl3d YRQx4ccneSS05XBb04qQWT46MJ1oYfxSiVF0Ar99rDlXBeF8AAJxT0ZqNQB4ebu1 Z/SulG2Kj/42NJSXwGiAJopwCsNa8QbTMxLVTqR8gQXQxbVRcQLFEv8FFNTVibum ywEqV6KV83DMaYENDlR0Z4capM5AjfjgiPwGaYnRqMTOvsssrYqlIfcdMgbXJzOG ztHCTXdWpCeeNLZ1dXMTeACYOHNueQ== =8SVO -----END PGP SIGNATURE----- --=_ff964d91c30bb1634691318312b877ef-- From nobody Tue Aug 20 02:39:10 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wntvj4VtGz5V3lG for ; Tue, 20 Aug 2024 02:39:13 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wntvj40Sbz45T0; Tue, 20 Aug 2024 02:39:13 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724121553; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=cApD/Zbfsuq35OCU+oruhEaby6rVETXK3W/AmOCT5kI=; b=eYS1g0HZTMqI+aMXwO7limz2AL9mVXxC/58MbRvKuclhoUdSIgSEtkqXKX3V3XpeRddHNx IX5mXjTFfQnOgFEpWkDW7BhiEYhhtztLIMBA37E0ohtz07vX1QRBfsI+ywMxxcAq68ag7G vdDDwFVd7qUgaUgJfv/6eKNbmZmb75fbf9iGvF56d7gj56C8AQbT5kzrOcuRdca9Vxjt4N yO2LSqyuJ5e/wRN/yT2h+axdcFcrCMko/sKjJKMOXAALq0RmHE8QOboHU9YfgpimfnbmR3 0P1PoNuSkOZRbEivUEhB32NlIQx1CSUucAhuZ4l0yylUcd7AYqgVeJB9Tq1mYg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724121553; a=rsa-sha256; cv=none; b=LLQuJAaLIqbo3JLhG2EucDNbO4GUMn5J1wycpudOdD0cDjlsNQg0jCKaeeZEaJkS5zsYQr zGeUqeSdNhX8i0ZtdKIZF22uwYo4h3OgC1I5C4Vrz+sXLij4FiCBe+ijQGuktaBh8d1OXs 3VaBmWNpWRtH8iX4AAcr6H2lYr810m4934KpKeM1ibWkuKl4gfkVL7Pe597ckcvpjCHCMF aI63mn54FfDwTrqzWgQYCr5jcmxb6vFatVjyKh7OGT/Rxr5f/333YKJaC6CY+Huu3Wlw9W n9PH+Z3YoF1t1tZSjYVF+C9niK+30lDvUz+nXd4qx0p4I37BtPo2giHvDPq4DA== ARC-Authentication-Results: i=1; thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724121553; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=cApD/Zbfsuq35OCU+oruhEaby6rVETXK3W/AmOCT5kI=; b=eXU/NjDOkNLgIMegAOctb9rLtNlC0+8ewgiut+luHUHMa2JIbCCXHwBjryf7nsmmpC+Jjg ko6WFP3XrgFuyLNfE3YWD4vkTtq4qv+uB3mAZPC0rK4jdpqqcC4VahUsxn8PFQc4hhqQ2a lrLeD5AZtGXPCkjWugdoGN3fM8EBV6wbvtt2VpGSrGVKkujnvohU15fy08uakUbAIotk27 A9X1BCiSZAYazUOPY2iUlV/87qNjgGu33+WMqcX2eAF/PtGceCY3bvYWd7qZMcnmL/g02g klvq7b0lCDGuwpHgiaBVTRUdev66/hV+PHE85WIX4adhCgTcOeBbzzR7Jml2Eg== Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.lerctr.org", Issuer "R10" (verified OK)) (Authenticated sender: ler/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Wntvj3T3Vz13q4; Tue, 20 Aug 2024 02:39:13 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=ler2019; h=Content-Transfer-Encoding:Content-Type:Message-ID:References: In-Reply-To:Subject:Cc:To:From:Date:MIME-Version:Sender:Reply-To:Content-ID: Content-Description; bh=cApD/Zbfsuq35OCU+oruhEaby6rVETXK3W/AmOCT5kI=; b=Mb185 gvvKp8hIDyWbA2HIxA7jhUTAPgE2qizLenwFxW4JALsWjYvHE5mHpzfn+9VX32U0gi5vA1UCeAhbV eOGtf5cNhiwsHlP0BViMC6cwofsKLcFAsGJgWKGfH0KP/TejKaCtYhZOiF8dTwFfvxoWP5gf3w/3Z Cp3m1RihqW92BNJFSM6GH8rUc4SU0XouuPuicVEmod40DjGjXG6bzLmD4Y0ZnQlz+5WZXWLfUN5pF yLXXwK1Rt9b2xBjS23siiT7FOwHgI2IRhd2N4zXaZS7PMkLTCQ2g4vEdHIY0AiNnhsHXI3qvjzd4W juCGH84rbXE8jKwFMRsO/t4MaWYkA==; Authentication-Results: thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none Received-SPF: softfail (thebighonker.lerctr.org: transitioning domain of FreeBSD.org does not designate 192.147.25.65 as permitted sender) client-ip=192.147.25.65; envelope-from=ler@FreeBSD.org; helo=webmail.lerctr.org; Received: from thebighonker.lerctr.org ([192.147.25.65]:21787 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.98 (FreeBSD)) (envelope-from ) id 1sgEhu-00000000OKy-0QTv; Mon, 19 Aug 2024 21:39:11 -0500 Received: from syn-070-123-041-087.res.spectrum.com ([70.123.41.87]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Mon, 19 Aug 2024 21:39:10 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Date: Mon, 19 Aug 2024 21:39:10 -0500 From: Larry Rosenman To: Larry Rosenman Cc: Freebsd current Subject: Re: RTL8125: wont stay up In-Reply-To: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> References: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> Message-ID: <093c92b6b67b4afb85c7ebc2cbc4ffa7@FreeBSD.org> X-Sender: ler@FreeBSD.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 08/19/2024 9:14 pm, Larry Rosenman wrote: > shows up, doesn't ping -- ifconfig up brings it back for ~4 packets > > ifconfig_re0="DHCP" > ifconfig_re0_ipv6="inet6 accept_rtadv" > ipv6_activate_all_interfaces="AUTO" > rtsold_enable="YES" > > 15-CURRENT as of just now, port of net/realtek-re-kmod as of now as > well. > > Ideas???? ler@ryzen-box:~ $ cat /etc/rc.conf hostname="ryzen-box" sshd_enable="YES" ntpd_enable="YES" ntpd_sync_on_start="YES" #powerd_enable="YES" #moused_nondefault_enable="NO" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="AUTO" zfs_enable="YES" ifconfig_re0="DHCP" #ipv6_activate_all_interfaces=”AUTO” #ifconfig_re0_ipv6="inet6 accept_rtadv -ifdisabled" #rtsold_enable="YES" smartd_enable="YES" kld_list="filemon" if I enable the ipv6 stuff it breaks, the above works but of course no IPv6. -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 From nobody Tue Aug 20 03:30:07 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wnw2c2QNvz5V7Cx for ; Tue, 20 Aug 2024 03:30:16 +0000 (UTC) (envelope-from grog@lemis.com) Received: from lax.lemis.com (www.lemis.com [45.32.70.18]) by mx1.freebsd.org (Postfix) with ESMTP id 4Wnw2c03JNz4DRc; Tue, 20 Aug 2024 03:30:15 +0000 (UTC) (envelope-from grog@lemis.com) Authentication-Results: mx1.freebsd.org; none Received: from eureka.lemis.com (121-200-11-253.79c80b.mel.nbn.aussiebb.net [121.200.11.253]) by lax.lemis.com (Postfix) with ESMTP id DDCE328140; Tue, 20 Aug 2024 03:30:08 +0000 (UTC) Received: from hydra.lemis.com (hydra.lemis.com [192.109.197.129]) by eureka.lemis.com (Postfix) with ESMTP id 365D726359E; Tue, 20 Aug 2024 13:30:08 +1000 (AEST) Received: from hydra.lemis.com (localhost [127.0.0.1]) by hydra.lemis.com (Postfix) with ESMTP id 35DDC13AA4; Tue, 20 Aug 2024 13:30:08 +1000 (AEST) Received: (from grog@localhost) by hydra.lemis.com (8.18.1/8.16.1/Submit) id 47K3U7ua070180; Tue, 20 Aug 2024 13:30:07 +1000 (AEST) (envelope-from grog) Date: Tue, 20 Aug 2024 13:30:07 +1000 From: "Greg 'groggy' Lehey" To: Larry Rosenman Cc: Freebsd current Subject: Re: RTL8125: wont stay up Message-ID: References: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ipYBJSWFXP1twoSB" Content-Disposition: inline In-Reply-To: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> Organization: The FreeBSD Project Phone: +61-3-5309-0418 Mobile: +61-490-494-038. Use only as instructed. WWW-Home-Page: https://www.FreeBSD X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20473, ipnet:45.32.64.0/19, country:US] X-Rspamd-Queue-Id: 4Wnw2c03JNz4DRc --ipYBJSWFXP1twoSB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Monday, 19 August 2024 at 21:14:58 -0500, Larry Rosenman wrote: > gpg: Good signature from "Larry Rosenman " [expired] > ... > gpg: Note: This key has expired! > > shows up , doesn't ping -- ifconfig up brings it back for ~4 packets > > ifconfig_re0="DHCP" > ifconfig_re0_ipv6="inet6 accept_rtadv" > ipv6_activate_all_interfaces="AUTO" > rtsold_enable="YES" > > 15-CURRENT as of just now, port of net/realtek-re-kmod as of now as well. > > Ideas???? Not much, unfortunately, just a "me too", sort of. I have a box with the 8125 on the motherboard and a second Realtek (gigabit) NIC on PCI. I've had issues with the second one locking up using VirtualBox on heavy load, and to try to track down the problem, I've switched to the 8125. The results were *much* worse. What did I do about it? So far nothing much. But my overall impression is that realtek-re-kmod is flaky. I haven't entered a PR yet because I can't be sure where the problem is located. Greg -- Sent from my desktop computer. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php --ipYBJSWFXP1twoSB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSaG4ICvM64RvkvCawi5vKQUHpCIwUCZsQNvwAKCRAi5vKQUHpC I/O1AJ9eL/Z+P59GrT8mMNzU0eGvZd7dugCfVgxyw2RdApAj8cCL3g7O1KDLgzI= =EV8M -----END PGP SIGNATURE----- --ipYBJSWFXP1twoSB-- From nobody Tue Aug 20 06:08:33 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WnzYr6b77z5SNDB for ; Tue, 20 Aug 2024 06:09:04 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-vs1-f49.google.com (mail-vs1-f49.google.com [209.85.217.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WnzYq3qNQz4YTs for ; Tue, 20 Aug 2024 06:09:03 +0000 (UTC) (envelope-from 6yearold@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none); spf=pass (mx1.freebsd.org: domain of 6yearold@gmail.com designates 209.85.217.49 as permitted sender) smtp.mailfrom=6yearold@gmail.com Received: by mail-vs1-f49.google.com with SMTP id ada2fe7eead31-4928fb6fdceso1560055137.3 for ; Mon, 19 Aug 2024 23:09:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724134142; x=1724738942; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Uj5g9GrVejlIubjFPkTpDore/bEk2J5ZH0tQHcfHdII=; b=k5mf4TPWKILwMgxl4JoMfe2tq0gg6UAI0AG34pxIT0nE3W7idT7yfYxbLpYFFXxZg0 XhlFarJBj4vy2FUhAFrPJ4dRBlVdygD8F8wxX/nJe6edb3z1LRx1kN8rXPTaIafFIJEu nr75XEoZSgoP6K83qZOsj05nRbdxeOtYTu6kpxuDo5AIIJEATzxKG4fFhRQdsjsm5lVQ rAh5a5wIoI7TX16f+TYRXSWcMdk9CUxM6+F0PUNH4IVIIJya+odXYuKxqxXWxaFk4Yqx ifVxTRgPQ1hm5d3ktGKcgpsePCAZD9Qcl3kraywCbKUJn3vFCVOVrO6twqcp7vwugCLN c1Qw== X-Gm-Message-State: AOJu0Yx77uEtxws/cloe0OoY52VvhsQGY4CA0sbmgvLXEHPXyWATcg6z nCy9+5WWG9CVy2C3TuUoLC1HTvZ9UpWZmqv0QzAqpx8wB2Z7aQxgaTJ4SA== X-Google-Smtp-Source: AGHT+IHYvnBLf3DRiUw2i5hge9bfxYH1H95BQP4F8ioiI+ilg6c+mYt/grgUI7n2BBgX24tLkyowJQ== X-Received: by 2002:a05:6102:2ad3:b0:492:a11f:a878 with SMTP id ada2fe7eead31-4977997d48emr15992924137.23.1724134142007; Mon, 19 Aug 2024 23:09:02 -0700 (PDT) Received: from mail-vk1-f176.google.com (mail-vk1-f176.google.com. [209.85.221.176]) by smtp.gmail.com with ESMTPSA id a1e0cc1a2514c-842fb72f79bsm1400317241.12.2024.08.19.23.09.01 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 19 Aug 2024 23:09:01 -0700 (PDT) Received: by mail-vk1-f176.google.com with SMTP id 71dfb90a1353d-4f6ac477ff4so2807118e0c.3 for ; Mon, 19 Aug 2024 23:09:01 -0700 (PDT) X-Received: by 2002:a05:6122:308e:b0:4f5:26c6:bf31 with SMTP id 71dfb90a1353d-4fc6ca09b55mr15266693e0c.12.1724134141311; Mon, 19 Aug 2024 23:09:01 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <20240819190714.mtYVCmQC@steffen%sdaoden.eu> In-Reply-To: <20240819190714.mtYVCmQC@steffen%sdaoden.eu> From: Gleb Popov Date: Tue, 20 Aug 2024 09:08:33 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: a zfs thank you :) To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.78 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.88)[-0.879]; FORGED_SENDER(0.30)[arrowd@freebsd.org,6yearold@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; MISSING_XM_UA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_NEQ_ENVFROM(0.00)[arrowd@freebsd.org,6yearold@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.217.49:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.217.49:from,209.85.221.176:received] X-Rspamd-Queue-Id: 4WnzYq3qNQz4YTs On Tue, Aug 20, 2024 at 12:18=E2=80=AFAM Steffen Nurpmeso wrote: > > Jan Bramkamp wrote in > : > |On 31.07.24 17:02, void wrote: > |> I was pleasantly surprised when I installed a new [1] zfs-on-root > |> -current > |> to rpi4 that when adduser was invoked, I was given the option to > |> encrypt the homedir. This is a great feature for my context [2]. > |> > |> It doesn't automount on boot but I think this is more of a feature > |> rather than a bug. One can have a different password to the GELI one = used > |> to boot up the whole system. > |> > |> I have not tested yet whether one can have the user, once logged in, > |> mount > |> their homedir with doas(1). Right now, I mount the homedir like so: > |> > |> zfs load-key -a (prompts for password) > |> zfs mount -a > |> > |> as root. > |> > |> I could I guess make a doas line for the user for zfs load-key -r > |> zfsfile/system. > |> Can anyone suggest any better ideas please? > > |There is the pam_zfs_key.so PAM session module that should do exactly > |what you're looking for if your users login with a password. It should > |similar to the pam_ssh.so module if you're already familiar with that > |one. Unless users provide the password there isn't much file system or > |disk encryption can do for you against hardware theft since the > |Raspberry Pi doesn't have any secure key storage nor would the kernel b= e > |able to know when it has been stolen and stop auto-loading the keys. > > To suggest a screen locker for "warm" security. > Ie here this is (on Linux, in /root/bin/zzz.sh upon lid close etc) > > if command -v X >/dev/null 2>&1 && command -v slock >/dev/null 2>&1; th= en > had_z=3D > for p in $(pgrep X); do > uid=3D$(awk '/^Uid:/{print $2}' < /proc/$p/status) > disp=3D$(sed -Ee 's/^.*DISPLAY=3D:([[:digit:]]+).*$/\1/= ' < /proc/$p/environ) > [ -z "$disp" ] && disp=3D$(xargs -0 printf '%s\n' < /pr= oc/$p/cmdline | > awk '/^:[[:digit:]]+/{sub(":", ""); pri= nt}') > if [ -z "$disp" ]; then > [ -n "$had_z" ] && continue > had_z=3Dy > disp=3D0 > elif [ $disp =3D 0 ]; then > [ -n "$had_z" ] && continue > had_z=3Dy > fi > act "DISPLAY=3D:$disp $SUPER -u $uid slock = /dev/null 2>&1 &" > done > fi > > Unfortunately there is no other easy way i know to lock all > X sessions otherwise. > > This is the problem i have with "encrypted home directories" per > se, i do not use that, but have several encfs directories, like, > say, ~/.sec.arena, which i mount via fuse as a normal user, and > $HOME is nothing but a symlink farm like > .xinitrc -> sec.arena/configs.git/home/.xinitrc > so before i mount this that is all hollow. > The zzz.sh script also does (simplified) > > if command -v encfs >/dev/null 2>&1; then > grep encfs /proc/mounts | cut -d ' ' -f 2 | { > while read line; do > act "{ sync $line/.; umount $line; } /dev/null 2>&1 &" > done > } > fi > > so that all these are unmounted upon LID close etc. (Unless some > process uses any directory within as CWD/pwd(1), then not. Force > unmounting does not work.) > > Ie that is all pretty uncomfortable (it is even more complicated > in practice), but like this data i care of a bit more is not > mounted when the LID is opened. (And data i really need to take > care off is never mounted all the time. And "of course" the hard > disk partition as such is also "cold" encrypted.) > > Ie, i just feel better that way. If you steal the laptop you can > switch to another console, and, i mean, here is no automounter for > USB sticks or what, no code runs then (i hope), but i do not know, > but anyway, if all that time an encrypted home directory of myself > would be unencrypted, that feels a bit odd. > > Anyhow. To remark that PAM sessions can easily be bypassed by any > shell script (script /dev/null 2>&1 &), and, i looked > at the ZFS PAM module in particular a few years ago, it did not > do anything REAPER-alike by then. That is "script" may be running > when the ZFS user logs out, and the PAM module will then likely > unmount the ZFS home directory. > One should at least hear about this situation once. > > It would be cool if the PAM implementations i know (Open and > Linux) would consider adding a dedicated session reaper, with all > session related modules stopping doing lots of dances, but instead > relying on some generic PAM library support mechanism. > Sounds a bit like a sophisticated and relevant Google Summer of > Code or something project. It feels like you're reimplementing ConsoleKit. I'm not sure if it can react to lid closing out of the box, but it manages sessions and locks/unlocks them depending on circumstances. From nobody Tue Aug 20 07:08:46 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wp0tn632nz5SThg for ; Tue, 20 Aug 2024 07:08:49 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wp0tn5X4qz4f9x; Tue, 20 Aug 2024 07:08:49 +0000 (UTC) (envelope-from grembo@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724137729; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+bjerrJht8KcQUB8ZoYWS31rbnsbJgpdPPeaDyo+APk=; b=pnCY+yQ5lyauwzTk1qyQmw1FMpizqUzXQU1S+ZrXrTFKR05DgH4L+RHqUH0KLVCcAqa2UT yYLEa+dz3MeoSB0v6PBmbTAsT1PBBT95gn94hop5yVMaykVcLTNMWzoOAO6w35QAR5O49d 2Q05hLH4WSkImUVWaOq4AUzVnxJNKISJ6jggJ4/0nWEPNlwv0Z6/hxcqNRZRyymDvlBCro k353zfJ2/CMnmqJqPnvqZBRcVYKdFpf1/eh634T+yamoXNHDv+v2k1AqIwHFPdzjDsBbui 8+LvClQQQAL+8tKiOSd9BTGJI+AEaPQWYxBdhhRdvyn3hyU4yBJ7fvlkpnvkbw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724137729; a=rsa-sha256; cv=none; b=h7309Lx5L1c3hxaqOswUG1TZ3THLgMJvbgnCpubVqNrx0D3IWYc53hCuESblEopTByvkHO ODLVs6KwTv8iMMmfPrGK83f8oRIupZ/nW40xLuaTKopzVDvFIagqD4BI8xXMI//8xGNPS6 V4xzzFE1ewZGBr7j4wGgg4mudnfGqwSf+ipcSTIx1VzvYEdpcALNDHAGTqPS10CYCF00Em Bhq7JGuGBgl8n6nByGtzOvqOdKdSWm9ZVKJCcnJkx7tBtO2osblcti7LtR6b3anPKQGMxF yTf+lmm7h2gEbEwNnpy5VRp48NnAVUA4w/PZZopJROZPvchEBIJyfidzFYgQLg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724137729; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+bjerrJht8KcQUB8ZoYWS31rbnsbJgpdPPeaDyo+APk=; b=pxSMXL3ik6c+lkzQ25dRRI3+RlHgYoVZjR5BGgHYOoG4iqMGU+U0PE93VvhzVrLTpDIknh f6XJ5eoMle9PLAUHUIaJ6iZFfaTFminbAj3IlCR4gS1nU1ul4M5Tk185BrDWeOwlCj+VOX adJqPF7zYy15y7HM1TYjI8ycnSnCzINdeZu1wFAAHp1owDOm+Ep9yIhSS8K4QihAh5kd6j GHU67jbrlIqlkwt/EuYlQGa6MwNe8l4cYBIjGZM/4+hSQ+5k072wbd9UIKix9WKOTa7L+5 9l6PHN0lGCjcLfVcYVYA9unhLFmTXqVuMY8x7dYc01ZSpLSFZpoeR29L7T+DxQ== Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.evolve.de", Issuer "R10" (verified OK)) (Authenticated sender: grembo/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Wp0tn2LNTz186l; Tue, 20 Aug 2024 07:08:49 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id 709197c2 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 20 Aug 2024 07:08:47 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 (1.0) Subject: Re: RTL8125: wont stay up From: Michael Gmelin In-Reply-To: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> Date: Tue, 20 Aug 2024 09:08:46 +0200 Cc: Freebsd current Message-Id: <60CB3128-E2BD-419B-BD02-B32ADA5AFA32@freebsd.org> References: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> To: Larry Rosenman X-Mailer: iPhone Mail (20H350) > On 20. Aug 2024, at 04:15, Larry Rosenman wrote: >=20 > =EF=BB=BFshows up, doesn't ping -- ifconfig up brings it back for ~4 packe= ts >=20 > ifconfig_re0=3D"DHCP" > ifconfig_re0_ipv6=3D"inet6 accept_rtadv" > ipv6_activate_all_interfaces=3D"AUTO" > rtsold_enable=3D"YES" >=20 > 15-CURRENT as of just now, port of net/realtek-re-kmod as of now as well. >=20 > Ideas???? Did you already try net/realtek-re-kmod198 ? -m > --=20 > Larry Rosenman http://people.freebsd.org/~ler > Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org > US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 >=20 >=20 >=20 From nobody Tue Aug 20 07:55:59 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wp1xH4pl4z5SZfm for ; Tue, 20 Aug 2024 07:56:03 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wp1xH4B7Hz4kWP; Tue, 20 Aug 2024 07:56:03 +0000 (UTC) (envelope-from ale@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724140563; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YunGk6fRpjQHcxQUrHQu5aaNhQ3Z/6BA+3V0bjgCeF8=; b=u5s/6b4BwReTnI6FaZFw6C8vQMxnHtHGD/WatnnW6QsGbnn/rRutXiKKuxpjycQCs6h9mG JrdoojqW11gH3VF6i1BCB6rsEwq9Lv9o6cfRVGq2KC2OpzCA429a8HlhNyHfWKj9eoNdgP CN4Pa/Ffo73PfQUb8yiwE65u//Cek3mCNYAmPp9owcaOmvRyte9ycP4FU53smH6f5D4n8I /dWkdua3n6sjjBC7hfT2QKUvUmFdp6wOai9UzJ7M8EVstv1Rl/8rkT1Vmjc2F84zjIvSKg BwFOIdnCTWPHNIWm3FqkTFFkC6jDeCBw52Ru1RbTZzCh5CVL2EXdxXJ4QgqVmA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724140563; a=rsa-sha256; cv=none; b=apxGD9YiM3Qsvui2w+C5Ha0JrBJ83X60WrsY3B9oFbvi9lBWz6hPHLmnUAhqaDbu1HrjNX /QX4w9Y5jfUOXv+/JrZKcIBlUuTmWyijXzu/cqPnhMNd+zAhmt20LlWRgo/WKjy8sIhh1N HrD0Fs43Sb1OGnJtdnOQhd2LTUtYXE3hghvDhr7wlupsNEg0RxqkPQUPAzJLgSmJEK84bS hxyKYezm1MuyWR2aK4v+v47vIoU2XSx4mJa1QZPYRoi2+A2pG6YvYIl6Cq8sgwbqQSA43i N0RA/htln1F7QqKI5nFeRF1aqgKrsY+rxN7CDorhEeevT4rHje3pAExa29YJ9w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724140563; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YunGk6fRpjQHcxQUrHQu5aaNhQ3Z/6BA+3V0bjgCeF8=; b=KuautypEvAmBJ3EkGJ+9QjCNzCZIiu/NBGvbgB+izyXcnXjswqo8chsF4JS+3eNy8DpIFX l26CI5Zeu4NvIpdhVPpeReA9Lpeei5L5Md6imRMIhGFV9H8uxw2YL90DkfstWo6wtJXh/M d8NH17P+se3eW45WrreTCJn7FyiL5G3IYcfwLKUsxs4yxM1rQgxpeT8zeVyB247fTbbWsu 07qqwxk5FtR5W13JuDm51WTPnYO1s8HDmSed89FBEWcCDagrYOz8oOf660obeixqo0uIFy /q82islfv4csGE/Ur3XXP6hjVGpiyWjiBdwIASy5pRUCS9vyVSjOm5CodhfAUA== Received: from [192.168.0.136] (unknown [46.188.169.109]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: ale) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Wp1xH0P81z19pC; Tue, 20 Aug 2024 07:56:02 +0000 (UTC) (envelope-from ale@FreeBSD.org) Message-ID: <01888623-0ec8-401a-bb40-378db5707c53@FreeBSD.org> Date: Tue, 20 Aug 2024 09:55:59 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: RTL8125: wont stay up To: Larry Rosenman , Freebsd current References: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> Content-Language: en-US, it From: Alex Dupre In-Reply-To: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 20/08/2024 04:14, Larry Rosenman wrote: > shows up, doesn't ping -- ifconfig up brings it back for ~4 packets > > ifconfig_re0="DHCP" > ifconfig_re0_ipv6="inet6 accept_rtadv" > ipv6_activate_all_interfaces="AUTO" > rtsold_enable="YES" > > 15-CURRENT as of just now, port of net/realtek-re-kmod as of now as well. > > Ideas???? You might try disabling checksum offload and report the result: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275882#c44 -- Alex Dupre From nobody Tue Aug 20 08:16:57 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wp2Pz54pxz5ScVC for ; Tue, 20 Aug 2024 08:17:27 +0000 (UTC) (envelope-from danilo@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wp2Pz4fDMz4nGt for ; Tue, 20 Aug 2024 08:17:27 +0000 (UTC) (envelope-from danilo@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724141847; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wfaGRdrJXmUR2dNmvTfsMNKWvc89LrR2J1Ltuxi6dWc=; b=oHVuq5oIJXhub9Dks5FA7RGvmjvDzIvv6hPhUlThKn6WuQMBLLxyo2cUBpMhssK7Wmsnar pcQZAUKwJlPQ4IThDJnLCL8wqneRXIv+m52HE6B3r+FjdLegFqL19aJDGua+LVRhSu2wmk /rWplxLZ+KC6dtBMg9CHZFxvDxrK6KgjQ0tiB4lPZ8dMlmqglSaIcQ2jMobSARi4MHVVz6 k1LTDukAFA1nkMFP0VRef1xNSk6GfmQ6rgcsLIiQqtXFqJ1XuEvMQE90o4oprOYyPhvuWs p02gfC1iHO/oCKzkatj6IF1u/PPTaEBfD7pD1zDwKkxmA7uMwEkI5jf0nqqX2w== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724141847; a=rsa-sha256; cv=none; b=CkTgbUttDK1DycFQ/G4cBEiwvNs3QvWtT6CgFLNpdROywVJkxgukFI5CeW8fsqMKlhtc3u HFcBM717GBcrUZK79sSnu3zTkpxc2SdLBDAMzEHaPc2N48l15LPs4ugs/A0KEkFGH7KGWy eJ6XlQQrMIko0LrNS9IYgPRyU3opOCXyzdIbP+htQ1r5kvNwie/T3VN0Gpq2CUgvSIuQb0 TclFbjZ9hAQ6YUaYzKSJklaP3mlncR3v95yIyoEzuQtabSAApt+oWa3WJDX8UPlAzBx7mD 8CufDxSZZNZ8OOkabiRQbtuO4IimsVm2Z5U541CFmtUmhKcB24zAguvpdarqUg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724141847; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wfaGRdrJXmUR2dNmvTfsMNKWvc89LrR2J1Ltuxi6dWc=; b=v7wm9Iak0JvjBCBSxqs3uv2vuSHoj/8FvK870HAkhEoBpuHPewuRvEER/eVEvMVL8v8nY7 QBcT/UzgW3K4keFKTUQ+ieSrm5+7dQwF47Sxvb7eJhGUWBajeHHHEzqlArx7JwRbq3Tn/8 wzOEHn266iyy9b454zV3D466zdYbf9l88ldvuLGA/+INOT62Ket9BWzXrgzlhme++lwR4Y BrWGmMFvYpCOs6blqhhiq/lrqWLYVOCOWxsC8EXENLoXBbdDUrHcbe60+mDgRGA0XudPLd C/YQ5rzDdD7rtsLduuVV6ewAOUJTDuvC0IJZu0TRtP5Y9HsIwG3sr0XivMuNVw== Received: from [IPV6:2a02:8084:4f62:4c00:401b:1414:ca65:f71e] (unknown [IPv6:2a02:8084:4f62:4c00:401b:1414:ca65:f71e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: danilo) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Wp2Pz2X9zz19pV for ; Tue, 20 Aug 2024 08:17:27 +0000 (UTC) (envelope-from danilo@FreeBSD.org) Message-ID: <6a97dd5f-84e6-4576-8bb3-e95b368bccf5@FreeBSD.org> Date: Tue, 20 Aug 2024 09:16:57 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: RTL8125: wont stay up To: freebsd-current@freebsd.org References: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> <093c92b6b67b4afb85c7ebc2cbc4ffa7@FreeBSD.org> Content-Language: en-US From: Danilo Egea Gondolfo In-Reply-To: <093c92b6b67b4afb85c7ebc2cbc4ffa7@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 20/08/2024 03:39, Larry Rosenman wrote: > On 08/19/2024 9:14 pm, Larry Rosenman wrote: >> shows up, doesn't ping -- ifconfig up brings it back for ~4 packets >> >> ifconfig_re0="DHCP" >> ifconfig_re0_ipv6="inet6 accept_rtadv" >> ipv6_activate_all_interfaces="AUTO" >> rtsold_enable="YES" >> >> 15-CURRENT as of just now, port of net/realtek-re-kmod as of now as >> well. >> >> Ideas???? > > ler@ryzen-box:~ $ cat /etc/rc.conf > hostname="ryzen-box" > sshd_enable="YES" > ntpd_enable="YES" > ntpd_sync_on_start="YES" > #powerd_enable="YES" > #moused_nondefault_enable="NO" > # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable > dumpdev="AUTO" > zfs_enable="YES" > ifconfig_re0="DHCP" > #ipv6_activate_all_interfaces=”AUTO” > #ifconfig_re0_ipv6="inet6 accept_rtadv -ifdisabled" > #rtsold_enable="YES" > smartd_enable="YES" > kld_list="filemon" > > if I enable the ipv6 stuff it breaks, the above works but of course no > IPv6. I had exactly the same problem, as soon as I enable IPv6 everything stops. Disabling checksum offload [1] "fixes" the problem for me and IPv6 works reliably. [1] - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275882#c44 From nobody Tue Aug 20 09:20:29 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wp3pq6Hzvz5SkGH for ; Tue, 20 Aug 2024 09:20:35 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wp3pq5Pvyz44Gb; Tue, 20 Aug 2024 09:20:35 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724145635; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=DPho8+jw1GjpU2Rfxop5EfxTAgjcnid2N61+5U3MC+s=; b=QD5DyqiDTTh+A39Ng61l2vYTZs+RnETSHtTeI38gHGcYgw9lhBfh3ezZ8L5UVUrKfJAZ5w HT/LPAXje/94Qy5UL16f1kHFGikiWXIdQ2eh9ssTrPUc/l1vGFJbDZ4xb4OJ1E52xWeJVt 1It+xLjLumyJW5/dvBAlI+T8rmSNaMQ6eZ/HhKLrhwSP7a5LeorAX2V8UaYMUgRHzfRam6 2ZAxwqWa4BdiJ/W60KeBXDzyFK5uuPFskmvM0PSxH/m1f5GiRXv0m1MrmzF+jbgOukpDa9 /jCQwZ4t45YCQ9kVfNn+R4MxUgTTkz92/wzG/S2L83KGi1VLRmJXQQJw8+YQvg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724145635; a=rsa-sha256; cv=none; b=KMJUG7/U4j8Ozl5Kk8CMMj/nkyGnLHDUlNxrKwx7zRz0ryJDU3D8z+f62kstrL9iIIDOJQ aWGVjYfQxXSYFUupELaylTd1gmd7G3QAaiY2w7xY/eZAZkJMJyo72Vl2s6exSUjc8m0Ya2 4SqV+06bNYBzfumoroKRz/elvtzDOZDQfCGtfw7A9/AfDoph1yiYQwGc4zouOK0SVxYZ6x zxL+Oi5eL6surY1MSqigDDPA8LbfAz/j4j4EwcV6lJMINZqkxpqrR6zKYeRx42alInoIx4 fuGmX4f4iVL0DcGigok9RrJxPvH5r/EwJ3bv3Dsz2yi1qbBSDiUvBZU3xYQDXA== ARC-Authentication-Results: i=1; thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724145635; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references:dkim-signature; bh=DPho8+jw1GjpU2Rfxop5EfxTAgjcnid2N61+5U3MC+s=; b=R/ik03NB0+XOBEvZ9jiJ9Cw4TJ1867VkiN+rx4kiB9aYT6ObZ/92OYzAWarGt1+zjJPj2r aWo5DaIVZ3cPoH4Yt09yb3FQfes7ERE17I+1iaI4v9oNAd7i8YogfA2/8esr4ax5bKCwR8 Z8nCmuW3fIjp+t+nQT4HFVaoLwmeulk95P9Vmlpkh8IXLwVtN14ZoUUWGB4Xjwu+l0HDWq Y4O+1Stao0jPEKfqTBFGWikXCUeaHhrrSfI3gqsv2AvcZBZ79N4LRmGCPfCI5p3WmRxUHh E+vnUFcjqKlsN6C2LIZOndhUa6trxMIXZ4wWl2e+GvCCdsJ2tKSlSfeaIMT1Sg== Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.lerctr.org", Issuer "R10" (verified OK)) (Authenticated sender: ler/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Wp3pq4kv9z1BYv; Tue, 20 Aug 2024 09:20:35 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=ler2019; h=Content-Type:Message-ID:References:In-Reply-To:Subject:Cc:To: From:Date:MIME-Version:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=DPho8+jw1GjpU2Rfxop5EfxTAgjcnid2N61+5U3MC+s=; b=yHVfa uHpAaQPXBfOCyuku4EAk5GohBHeaf0SJqguDfOHAYu3yJuYYRNDmhiLcyBmGYbMtBiAml4be6VRE1 UVsUR0ZcjxrQYixKKJF18BKxmH07cy9jFC9mIZYPYgqu2HXu7nLcSLlw0MvpKX7w+eToW4LYs0P0G iyu2FWvvxcQnSSjR7ZBwEhH7BqNgUMU2bjfxls3gM+18OUNcAgEs/hzUdyIR0TzIYBF8oARbbK+lh joJi24jNQnlgi/EHC7hNvm5f1SFkMmOJVLI1R6wdog0cmjv4SNwBaYu51hFWYt4ON+h1s5tw/XDIi /pINJlYyNcSOkFDFBoL/il6V7wzWQ==; Authentication-Results: thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none Received-SPF: softfail (thebighonker.lerctr.org: transitioning domain of FreeBSD.org does not designate 192.147.25.65 as permitted sender) client-ip=192.147.25.65; envelope-from=ler@FreeBSD.org; helo=webmail.lerctr.org; Received: from thebighonker.lerctr.org ([192.147.25.65]:13919 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.98 (FreeBSD)) (envelope-from ) id 1sgL2R-000000003VL-3Idg; Tue, 20 Aug 2024 04:20:32 -0500 Received: from syn-070-123-041-087.res.spectrum.com ([70.123.41.87]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Tue, 20 Aug 2024 04:20:29 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Date: Tue, 20 Aug 2024 04:20:29 -0500 From: Larry Rosenman To: Alex Dupre Cc: Freebsd current Subject: Re: RTL8125: wont stay up In-Reply-To: <01888623-0ec8-401a-bb40-378db5707c53@FreeBSD.org> References: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> <01888623-0ec8-401a-bb40-378db5707c53@FreeBSD.org> Message-ID: X-Sender: ler@FreeBSD.org Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_da0d0757fe723cd6caf92d3586901f10"; micalg=pgp-sha256 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_da0d0757fe723cd6caf92d3586901f10 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On 08/20/2024 2:55 am, Alex Dupre wrote: > On 20/08/2024 04:14, Larry Rosenman wrote: >> shows up, doesn't ping -- ifconfig up brings it back for ~4 packets >> >> ifconfig_re0="DHCP" >> ifconfig_re0_ipv6="inet6 accept_rtadv" >> ipv6_activate_all_interfaces="AUTO" >> rtsold_enable="YES" >> >> 15-CURRENT as of just now, port of net/realtek-re-kmod as of now as >> well. >> >> Ideas???? > > You might try disabling checksum offload and report the result: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275882#c44 disabling csum offload fixes it for me as well. -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 --=_da0d0757fe723cd6caf92d3586901f10 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=488 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEHjgknedhWzvJgwVzaXyZsatIp30FAmbEX98ACgkQaXyZsatI p336NQf/SBozEG1TqJGprQImfNFlL1AOCYHk8r2rzCH0wUmu6OLUnkHNrjbzuISD TKSUOXu3ROyhdaEKqffDJKLvWOF84an1dduGK3ElBU0lZvkqmcSTXAvSb9SCIR6z bgmARsSymXKu1V6mt7ZzmFYq7Fe9E6YAHTJ7xJZnS4DIwf0F9ZFG5qJp2OQwo5Vd qc3MSkZF9EXBFFqUoGWIYDb2DpwTOfs1TmaTeqKsWUABCqdrnZtKhXIQkvH81LHt D8+v2ofw81am7+v4+a5Hk794N7Olg2O5CclyjdIFzLDHMCJRJoPX2cJ52CRHj+K2 wqtxUpoti/R9HbNKy1dFiFUwFUvgPQ== =PvQG -----END PGP SIGNATURE----- --=_da0d0757fe723cd6caf92d3586901f10-- From nobody Tue Aug 20 09:21:30 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wp3r02RhGz5SkNm for ; Tue, 20 Aug 2024 09:21:36 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wp3r022YKz45LM; Tue, 20 Aug 2024 09:21:36 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724145696; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5VfMY/5/HpjouwHXDJJTBy4wKoTpmzCyftleb//a/JA=; b=arPaF3Le1HHKwamOIriIMQDEXLprdohxTKdXpF7XjtfkeRrzIf05QUQD5piDIf3g+y9EP4 6fxwK6FvvP8SiVCtbuBekVQ/AKMwOipyIoSh32naLzd6LnKR8gheayvUKVR9rqlS6yQuwb 2VtsJuWcuferxBzfyVI6sR01HB+8XiPpqEdnGGXex2hjYOWzMjiYFhthfrlkx1UWRW2yo3 RnbekrDorKVPylUapL2/JfDg8PaJqPVqbN6KbKFwunFBZ8Xa971VA1IJcUR8G/VyT5wQkR Bu2se+nYXCD5iUeDFAdrIAj6icCrze9kGlBxuoLo0dIqZZeo/2tYr6vNBqSHww== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724145696; a=rsa-sha256; cv=none; b=Ao9FEQ8d6J4jVt3Y5Xmg0DbvMDuc0KbFFF/LuOnT+8QZVtHzp5/KmXykALCDDp6cfho8eo 6Q1o9f6MF7QnQujiKkqeQYVSbejTBkSNIwUBGW02hQZDyvjVp4oUZjccdkHAfBBps/aJ6h ibJyHPJKZX+Iw1wTXMUiUHqEWRbDMT+yFxR2gJ+JtjrQG3fsK60Nq7lCmPR1bNe6sJgFpL s92Z+Pz507zm3m7I4rWQxgCKugMQ839a+m1KSiE42nyxNtLdvqqr7MrMCJo9uPuww72WaS XCqcQhwq5eL5I6RkLck0nAxzEG+fZ+rBhJlqVGnBONCJnk4vbwBe4r+uJl9EjA== ARC-Authentication-Results: i=1; thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724145696; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references:dkim-signature; bh=5VfMY/5/HpjouwHXDJJTBy4wKoTpmzCyftleb//a/JA=; b=usROw0clclWqhUk3t3LeBaYldhkb7VaISxm7esq74W+v+egZMw69c6bPeDGn+tSzdZYmWq QoOnlyP26G0vUBfri5k7Fhc9dMTMc0E1AK1HHeKrjTzYdjlopCP9n9iEyE9WZ+fVY+Kb57 HgLjAyo1AguGRR8vTPFHNJKPbWwsei+MOwv0I3Ch6+RGp0Bmxwtv67xpzEh+4u85CF2Ynz PIc6YD4ohmQ6f9z0SSiYY+VNf4UtM69D8+NUriwKw8WP3N6Y8bmvQjcV3a70xnl3UvgFBm R44FMj6iPwggXEPeTFUs29Ppg9YxgOC73zOqnPlXW/thd0H95qWvRNdDkBHFuA== Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.lerctr.org", Issuer "R10" (verified OK)) (Authenticated sender: ler/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Wp3r01fl8z18y3; Tue, 20 Aug 2024 09:21:36 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=ler2019; h=Content-Type:Message-ID:References:In-Reply-To:Subject:Cc:To: From:Date:MIME-Version:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=5VfMY/5/HpjouwHXDJJTBy4wKoTpmzCyftleb//a/JA=; b=VsU7H E6560o0XZfw9Qp6WTmEbr/gcb0TB8Q1RlSlK0S/wq8jd1F7GxyBHjbGr3KPxbS8LYc655e5w3c831 Pf7nPuch4FWRzml+h2K6k/HPHaQ/w0egUULyz9B/auCmhegWA1YAcpH+mwKiouj1/bmWUpQ5Dxwmu 7so9FBBP1BEWGWILVEW0hZgm7QRlDHlGFKdQok5Yv05CXMU/5jJiVZUV98F+D0cc7Xzqy1r/ZjOtg jiUXpEbFCl2dgjIo+IMeXfn4rhEHcIdDEXgXKRpi0pqpW93uwODqaNYetFORh0/nlLY1hHr3nmyDN Hhk7Qrq4KeSthE5oUrkwyglkjfhjw==; Authentication-Results: thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none Received-SPF: softfail (thebighonker.lerctr.org: transitioning domain of FreeBSD.org does not designate 192.147.25.65 as permitted sender) client-ip=192.147.25.65; envelope-from=ler@FreeBSD.org; helo=webmail.lerctr.org; Received: from thebighonker.lerctr.org ([192.147.25.65]:16216 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.98 (FreeBSD)) (envelope-from ) id 1sgL3R-000000003We-0NBP; Tue, 20 Aug 2024 04:21:33 -0500 Received: from syn-070-123-041-087.res.spectrum.com ([70.123.41.87]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Tue, 20 Aug 2024 04:21:30 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Date: Tue, 20 Aug 2024 04:21:30 -0500 From: Larry Rosenman To: Michael Gmelin Cc: Freebsd current Subject: Re: RTL8125: wont stay up In-Reply-To: <60CB3128-E2BD-419B-BD02-B32ADA5AFA32@freebsd.org> References: <88e3f79deb314fd3530c21c5b8d0b1ab@FreeBSD.org> <60CB3128-E2BD-419B-BD02-B32ADA5AFA32@freebsd.org> Message-ID: X-Sender: ler@FreeBSD.org Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_b93f1b5feaa735fd17b9f8358e378281"; micalg=pgp-sha256 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_b93f1b5feaa735fd17b9f8358e378281 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8; format=flowed On 08/20/2024 2:08 am, Michael Gmelin wrote: >> On 20. Aug 2024, at 04:15, Larry Rosenman wrote: >> >> shows up, doesn't ping -- ifconfig up brings it back for ~4 packets >> >> ifconfig_re0="DHCP" >> ifconfig_re0_ipv6="inet6 accept_rtadv" >> ipv6_activate_all_interfaces="AUTO" >> rtsold_enable="YES" >> >> 15-CURRENT as of just now, port of net/realtek-re-kmod as of now as >> well. >> >> Ideas???? > > Did you already try net/realtek-re-kmod198 ? > > -m I did *NOT*, but per suggestion from Alex Dupre, disabling csum offload fixes it for me. > >> -- >> Larry Rosenman http://people.freebsd.org/~ler >> Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org >> US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 >> >> >> -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 --=_b93f1b5feaa735fd17b9f8358e378281 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=488 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEHjgknedhWzvJgwVzaXyZsatIp30FAmbEYBwACgkQaXyZsatI p33E/ggAgES3gCAHxBL7sFYsrvZVuD4lHdiyd7l2sX6YhyW/aHaRquLa9QZmT8UQ M0cqmfSlAozidICdie5NEcAhKeAVQVR6JSFoOYAnFeJ/a/Z5hRhnEdBUsZrZQ+Mg uZvh6tXiFIum+B1smdTJexnEcE3HfjtgarrEgd4+pD9/4RfOWocSVG5NAwdiAZQ1 3U9yq+NVUg1/chkcjE3v8bzB2otIAWwI0l2jabYK8DIUvZMLGqVMBRzh/NcMxMNb 1nPiviSMRMKljM1lYxfTCacqofM+4RNVph1IAKCjkICLIRshrzk/79JXYUnS8HSa LnGlApLfL8dagAa5mD39Fo6FswY4QQ== =Y/ZU -----END PGP SIGNATURE----- --=_b93f1b5feaa735fd17b9f8358e378281-- From nobody Tue Aug 20 19:23:23 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WpKBW6wTPz5SRbD for ; Tue, 20 Aug 2024 19:23:31 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WpKBW19xFz4YHJ; Tue, 20 Aug 2024 19:23:31 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=citron; t=1724181805; x=1724848471; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: mime-version:content-type:content-transfer-encoding:author:from:subject: date:to:cc:resent-author:resent-date:resent-from:resent-sender:resent-to: resent-cc:resent-reply-to:resent-message-id:in-reply-to:references: mime-version:content-type:content-transfer-encoding:content-disposition: content-id:content-description:message-id:mail-followup-to:openpgp: blahblahblah; bh=LlWjrmPDohkJ1yINQisr06VpI7ui9z0kmfs4GOVglHE=; b=HWX+BjijnBnKk5GfclDei8qzxhqolaVRk4PiDEJzowbdkBvsFmg8z1GbtkzqVqu783x1IOJi 5upt2NK9+jHrK1cc++KeMdePNf4UvC8PUz5LQEc3soRE4YG/za4rqk5ur1ETNO0SterARhXNOP dU5NXibnVMxrSnYvBDMW/4df3tycmIhvcHHsCa+SaaRCux3HhdRhjsip5TYtXTlQQou+4RK7Si aBsFXdl+DK9LHw1ccRBJgUg52SPeSQ/7ML0aDa8D908HCD8CyoiOzoXyu1evr1hX9G4GAgayiD dIoQKtC5Z/uvYQA65CTdGh4PhPWcn3qxytdpuD88sAcjaI4g== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=orange; t=1724181805; x=1724848471; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: mime-version:content-type:content-transfer-encoding:author:from:subject: date:to:cc:resent-author:resent-date:resent-from:resent-sender:resent-to: resent-cc:resent-reply-to:resent-message-id:in-reply-to:references: mime-version:content-type:content-transfer-encoding:content-disposition: content-id:content-description:message-id:mail-followup-to:openpgp: blahblahblah; bh=LlWjrmPDohkJ1yINQisr06VpI7ui9z0kmfs4GOVglHE=; b=Nv5rYFKpAwLAGhzSw1h/8KEQY1mDcamZ5j/lwzffCVteyMgrBaJ7y0Ng8Uf62Pv6OQFFerYT CyLUYF2E4frwCw== Date: Tue, 20 Aug 2024 21:23:23 +0200 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: Gleb Popov Cc: freebsd-current@freebsd.org Subject: Re: a zfs thank you :) Message-ID: <20240820192323.OaLjIO5I@steffen%sdaoden.eu> In-Reply-To: References: <20240819190714.mtYVCmQC@steffen%sdaoden.eu> Mail-Followup-To: Gleb Popov , freebsd-current@freebsd.org User-Agent: s-nail v14.9.25-599-g5c75a327b2 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15987, ipnet:217.144.128.0/20, country:DE] X-Rspamd-Queue-Id: 4WpKBW19xFz4YHJ Gleb Popov wrote in : |On Tue, Aug 20, 2024 at 12:18=E2=80=AFAM Steffen Nurpmeso \ |wrote: |> Jan Bramkamp wrote in |> : |>|On 31.07.24 17:02, void wrote: ... |>|> [.] when adduser was invoked, I was given the option to |>|> encrypt the homedir. This is a great feature for my context [2]. |>|> |>|> It doesn't automount on boot but I think this is more of a feature |>|> rather than a bug. One can have a different password to the GELI \ |>|> one used |>|> to boot up the whole system. |>|> |>|> I have not tested yet whether one can have the user, once logged in, |>|> mount |>|> their homedir with doas(1). Right now, I mount the homedir like so: |>|> |>|> zfs load-key -a (prompts for password) |>|> zfs mount -a |>|> |>|> as root. ... |>|> Can anyone suggest any better ideas please? |> |>|There is the pam_zfs_key.so PAM session module that should do exactly |>|what you're looking for if your users login with a password. It should ... |> To suggest a screen locker for "warm" security. |> Ie here this is (on Linux, in /root/bin/zzz.sh upon lid close etc) ... |> for p in $(pgrep X); do ... |> act "DISPLAY=3D:$disp $SUPER -u $uid slock >/dev/null 2>&1 &" |> done ... |> Unfortunately there is no other easy way i know to lock all |> X sessions otherwise. |> |> This is the problem i have with "encrypted home directories" per |> se, i do not use that, but have several encfs directories, like, ... |> [.]all these are unmounted upon LID close etc. (Unless some |> process uses any directory within as CWD/pwd(1), then not. Force |> unmounting does not work.) |> |> Ie that is all pretty uncomfortable (it is even more complicated |> in practice), but like this data i care of a bit more is not [.] |> Anyhow. To remark that PAM sessions can easily be bypassed by any |> shell script (script /dev/null 2>&1 &), and, i looked |> at the ZFS PAM module in particular a few years ago, it did not ... |> It would be cool if the PAM implementations i know (Open and |> Linux) would consider adding a dedicated session reaper, with all |> session related modules stopping doing lots of dances, but instead |> relying on some generic PAM library support mechanism. |> Sounds a bit like a sophisticated and relevant Google Summer of |> Code or something project. | |It feels like you're reimplementing ConsoleKit. I'm not sure if it can |react to lid closing out of the box, but it manages sessions and |locks/unlocks them depending on circumstances. I .. do not know consolekit, but it does not look as if i want it: $ prt-get info consolekit|grep Dep Dependencies: dbus,gobject-introspection,linux-pam,xorg-libx11 (Funnily i do have the dependencies installed, gobject stuff for harfbuzz for mupdf, DBUS for iwd (wireless) and bluez.) No, but i am happy that noone wants to start introducing systemd into FreeBSD, i think it can do something like this. PAM sessions are broken unless anybody plays nice for sure, and with dedicated reapers that could be overcome. For my LID close things, there is software which allows paranoia, gpg-agent for example supports SIGHUP This signal flushes all cached passphrases Unfortunately i failed to upstream the same for ssh-agent, 'thus i have to workaround it (or patch forever). And unfortunately encfs does not support auto-unmount on SIGHUP, also. So it cannot be as easy as pkill -HUP ssh-agent pkill -HUP encfs ... called by root on LID close or so if one wants to increase "warm security" (i think this warm / cold terminology is from PHK). And that there is no general way that offers automatic screen locking for all X and console sessions on LID close, requiring password entry for unlocking, that is really strange. Maybe ConsoleKit can do that more easily, and portably so. (But i keep on using the simple shell script loop, as the shell script is anyway running on LID close.) --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) From nobody Wed Aug 21 14:29:30 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wppcx730Yz5TyML for ; Wed, 21 Aug 2024 14:29:37 +0000 (UTC) (envelope-from Matthew.L.Dailey@dartmouth.edu) Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2070d.outbound.protection.outlook.com [IPv6:2a01:111:f403:200a::70d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "DigiCert Cloud Services CA-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wppcw5B0Gz4GLP for ; Wed, 21 Aug 2024 14:29:36 +0000 (UTC) (envelope-from Matthew.L.Dailey@dartmouth.edu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=dartmouth.edu header.s=selector2 header.b=IQ3l4+kx; dmarc=pass (policy=none) header.from=dartmouth.edu; spf=pass (mx1.freebsd.org: domain of Matthew.L.Dailey@dartmouth.edu designates 2a01:111:f403:200a::70d as permitted sender) smtp.mailfrom=Matthew.L.Dailey@dartmouth.edu; arc=pass ("microsoft.com:s=arcselector10001:i=1") ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=o3UtOAzqZPJRKcd/WsVzfduKel55nsxI1k1AL8o3yUl9/bMQNabOw+dB/bENz+e3oZMB/uYtNdHzurA1GKJGf2IGyg8qbjDrqTf3NzKTiW3eDu7HTO1VTrZWXrjqaSvnX5oNrfXd4uPof6Xa5F+LODaFGln7bpsKIoyoN5V00B8ZY5bDYQrf+5UVIu1r0SeKulAY5aKMVYuYgkbUrcxOrWiqGoBb/3t3OsdHCFKg1SBQ6vHLIH1c3Oe57Af/4eHhRePAay6S+hEcaZRETqJ5P9p2TttqJ7C8tTLow+cD283XhNStcHuQMYyAthTLl9s9BornuDZyVwDttZ4s+sDXvg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=cG5MdVeRJakpse1vrRs68vFZkjWh76GJTemgAJHpOf0=; b=PBVJblS8i/mMnxT/OObKJq1w9PgMla8MMNDF584JFb4/I64WlY2hdbQ4EIctEKVu7l/jTavyyTtKJe5R5A6RaJM1l2sJYovL9B4UMt+I82d8oO323W+9qvLMMCTZ7rzDZ97wRAYtLr8XJrwVeEaNplAau3jfiVyknSrbX6qQUAD/TbelHkyROBQaZimZ/DeoAjZCWZUoDRbQOGugMMQyqapXylPTOdmE2zbgk88J4lK9zStjRMbu45hPxtdl9po9MISlNEjH9AbgvHh99E5RT6u3M0TTpg9GYbBK3DgKNs6HXnv9dDwHVeQyFaaGaVFWtuQ6SIhkCBncP4eS9oqSoA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=dartmouth.edu; dmarc=pass action=none header.from=dartmouth.edu; dkim=pass header.d=dartmouth.edu; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dartmouth.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=cG5MdVeRJakpse1vrRs68vFZkjWh76GJTemgAJHpOf0=; b=IQ3l4+kxDHdvqqMBH10pB/I+kEpvHc5QOELc/+0tPOoi18c+GY+5gip8H930rrmFDXXUKgHHVin6Ge2/iq5AgIFYs3NEzgT3zG3dGGraP5MDe9YAqsv3ILPfJMCv9zpbHVAf+GsLevTGZRdI08EPpMOTQu0JYvWdRTSmxD0i6QM= Received: from DS7PR03MB5574.namprd03.prod.outlook.com (2603:10b6:5:2c1::16) by DM6PR03MB5257.namprd03.prod.outlook.com (2603:10b6:5:249::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7897.18; Wed, 21 Aug 2024 14:29:31 +0000 Received: from DS7PR03MB5574.namprd03.prod.outlook.com ([fe80::5340:c731:1512:51d7]) by DS7PR03MB5574.namprd03.prod.outlook.com ([fe80::5340:c731:1512:51d7%7]) with mapi id 15.20.7897.014; Wed, 21 Aug 2024 14:29:30 +0000 From: "Matthew L. Dailey" To: "freebsd-current@freebsd.org" Subject: Kernel panics with vfs.nfsd.enable_locallocks=1 and nfs clients doing hdf5 file operations Thread-Topic: Kernel panics with vfs.nfsd.enable_locallocks=1 and nfs clients doing hdf5 file operations Thread-Index: AQHa89aIe8KNrui4i0WNFJFKDRPNEA== Date: Wed, 21 Aug 2024 14:29:30 +0000 Message-ID: <3ed15b15-6f1c-4290-a552-aaafef7cc82e@dartmouth.edu> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla Thunderbird x-ms-publictraffictype: Email x-ms-traffictypediagnostic: DS7PR03MB5574:EE_|DM6PR03MB5257:EE_ x-ms-office365-filtering-correlation-id: 8647cdd4-9f1c-4b65-289d-08dcc1edab19 x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0;ARA:13230040|376014|366016|1800799024|38070700018; x-microsoft-antispam-message-info: =?utf-8?B?ckg4eFZJWERFS2cyQ0E3OWMrSW1jTS9Obkd0NDZEcVhURFA3NEZxSEVUbk9p?= =?utf-8?B?TStubk40TUxJNEloVXVyazJtTjd1QkdpcTVvSG9jdHA0elc1N2dDdXgrUFUv?= =?utf-8?B?TWVHaWJuRFRJS3dKRlhsQTlzb0w4RHhvU2hHQ013bTlIUmtuOTZldjFJQkZx?= =?utf-8?B?UHY0ZG9MSWJKMytoL0pTYXgwWG5Hdi9DV0NhMnZkZUttUlZ1YUtwQnUxZ3lD?= =?utf-8?B?YmtYaEVHR2g3M05ZVnNaQ2VoNEUvWTkvTk5RaVJvalRUL0dnRjlqRjZ5dW5W?= =?utf-8?B?Vlg3aG1UTDhjR3VlU0NDWXFKUXVYL1hPL2Fnc0l1ZThXbC9lUE0zQ3FabSs0?= =?utf-8?B?a1FxV3BLMWN5Z1hYUlNJa0JsVUdETHhtK1piVkVIUVBBWnVIclZZTDRSNkJX?= =?utf-8?B?UmFKajZKWUtrbGR0MEM0ait0RC8yQW5JWUR4YVlRVm5LaGtnYVNFR3BzakEr?= =?utf-8?B?dWVJczZxQkxFTWpCSWRiZnVnRXJWQ0FvNVhTYzFsTmpnc0htbnhCS0xXSHdx?= =?utf-8?B?a2hCazU3amlLNTVidW9sZE53ZHNuZ2JGMUh6ZUR0ZWVpRHY2V0VWRUY0b0VB?= =?utf-8?B?SXllb1VlMk9pYWhNc08zZmZzUllRenJWNlNmZDFKMkhqM2kyOG9LcnB0SW1J?= =?utf-8?B?aE1saldHcSs1SEJtdnIzSGpZbVRyeG5iTVcwN0pGcnFLenBiRzl0Y2c4cjcr?= =?utf-8?B?VUdiRXVidFFjU09zUlU3ME96Z3lIeXRaWlU3WUVENUlVa0I4Z3NqdXZmanB3?= =?utf-8?B?ZW1aZmRaMXByZW9OUXNoWk94QlBwQzlWRjR1Znc1S0VYZE1GMm1oWmdHcTZ3?= =?utf-8?B?bG9EVG9wcFhGN1RiTnJEZmJLMUF4ZUVFS3pvK0IzbDRzaVhsQ2d2TVpmTGdT?= =?utf-8?B?Vzkxck1ITkxRdXlUVkI2MGtVTnFld0FkMnNFUHo5ZFQ4UDJ5aFZMVk1FMjNH?= =?utf-8?B?SUE3a3Z1T2I4cXRNS29JdW1XdG1tQW4yMm9qeEJDZVVOL0VpbFc0UTJWSkNa?= =?utf-8?B?MTNsVG9ORWMvRFNESVNzUnBwVkhYN0ZPY0trRzY1dlNQSDlkVjFIZUdnMEVM?= =?utf-8?B?bFR3T3owTlZaU2o0eDRBQ3NWUm45d2R4cThjdTJaa29mS3k0SW1za0kzSFRE?= =?utf-8?B?WmJRc3NtWFZUd2YxZjhVa3R3MjYxVVA0b0hmS0ZOeTdUZlh0YnIwK01PQUtl?= =?utf-8?B?OXM2VXMxRUtDVUx2L1lXbmRCb2czZU12K3laeDR5QVZ4NkJGbk1vemxsRUFs?= =?utf-8?B?Y0JoZkM5bzlqVWJZNWt4MWRvdzJJRlBzbFA1R1RqNlNoc0IxMncyTGVCOWpT?= =?utf-8?B?MXgrRzZpSzBZNFBmUHJuVS9XQTlqd1VTSTk3cUxhdWp2d2ZiZXRwQlpoeXRa?= =?utf-8?B?a25Vb2JRNUhVZkNXQ3pCZ0psbEN0bmFIWVdVZFlnai9qY0pubjhlNVNCNWE3?= =?utf-8?B?T1VvUjZqcEh0Q2xnZTl1T1pUekE0V1JSZEhJbGVuTWtZU25wKzBoRUcweEhk?= =?utf-8?B?TVgvWVB4N2VIZnFYOEl5TitUWFZaT2tXYWI2Ylp0dlRjd0tzWVMzeDBPQWE4?= =?utf-8?B?MDZzc1VwVkxqSGlmVis1ZG5sVDJERlVESTBpbXc0ZlRzaEpsbHpxSTVmUWps?= =?utf-8?B?OUNjRVVVbE5LekNKNFNlZXVoSnZ6U2VjYUg0RWM0Tkl6RHp4MEFwVld4a3Q2?= =?utf-8?B?MmIvblpzUkY0b1VwYVhhZG5hbzNXbktQMDl6NWVuUFJIY1k0VG5xN3N3L0Jk?= =?utf-8?B?cS9BQkZnNzRkTXV2QTJ6Z29QdnVhMEVxcHJUN0s4cW5qajlCVDR3RzhHKzJp?= =?utf-8?Q?R3Z8+S2lm1J/dqSZeOZen7mC62LP8DgdKU6iQ=3D?= x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DS7PR03MB5574.namprd03.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(376014)(366016)(1800799024)(38070700018);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?utf-8?B?SlhXZVVvSC96NFU5R3V5NVg4cFFhSExYNUc1Y25PUGxOK0RiUytndm96NEhH?= =?utf-8?B?cTAweGZmSlhOWnFkeTJ2K3JhR2V4NnhvSnQ5b3QrMi9yUjczTjJvYzJnVm5J?= =?utf-8?B?UXlpM2d3dHVHVnRFd3NONVZreElTM1orOG1FKzVoQzR1TDgrNm1xWFZKNGNK?= =?utf-8?B?dzBNL3MxY2VLNE1zbC9OanhuaUQ5YW1sL0hmZlBwK0laR2IxckRZRkxtMzZ2?= =?utf-8?B?WTg4akZKWUVuL1ZpaFF2QUEvSXZ1WnhWOGlyV1UydldNZE5NVXdnTWNXZUtZ?= =?utf-8?B?MHJqYUUrY1N0Ym9XRkQycDZNcS9BUEZVdkVGUFFUelp6YmtHWFVJWHdVTG9E?= =?utf-8?B?dEJIbXRRRkV1ekJoZkNxNzdkOWVRVGNsMXJhN0lmczFNWTR0Zlc2VTMybEdZ?= =?utf-8?B?UmthN0JXOG9hVHlLaEhUNExuNFc2WWdiVHR3SE1hZFFGTnQ4eTJqN3JqOXp4?= =?utf-8?B?d2hIWEN1VFFRQU5nY21ZNkhTaGU1ZGx2bE1Wa2NYZk1jbkdYZnI5RWlTTFhs?= =?utf-8?B?L0l1czJUSTNpNE1RYlduZTZKTHZselBadGUxV09MYzNPdVhPbm9zZzNLSEc2?= =?utf-8?B?LzJPcWN1TkluSndDYmFiRG1Uc0hhT25STk0yck5hNktXVU5XQmdPb1dhNDNm?= =?utf-8?B?SlQzd2ZoSjFYN3JPZUR5UVRrM0hYUlNVU3V2dkJMZnB0WGpQbUdsZWtKZUdR?= =?utf-8?B?MitrZ252L2Y0RjZnNjdSdFFvdGU1MkY3Z1d0L0dYWGFtUWpIMGUzaFhYSnFi?= =?utf-8?B?WVBNRXlnQ2dMZVRsUEhTK2xJOW5ETnQ5SVZxOWVlWHRobUdBK0kyeTZsRVhS?= =?utf-8?B?c2lROTBiNmdMSVJWR01MWVVraG05QU5sOEtqNGdVb09wNksrZzlkbFovc1NP?= =?utf-8?B?Z2ErVEFKaG5SdzVDeUhXell1YTcwckpIWXJhTFVhbzB2UmZkdFFKbisvMGls?= =?utf-8?B?K1JFSUNtejZ2SkZWbkw0OUMydTNFRGdsQkhsbm9zVWZpVmVYWUJ3Z3YrQVB0?= =?utf-8?B?RHhXb3Jac0xwNll0dXFHd1ZhRTBCYVhSQWp0YmNDbWU0bEcwRkl1dlNZMkFV?= =?utf-8?B?eHhuQW1IU2V0dlZLc1VxRFQvNVhjakdwWU0xSStuZkdYcUwzaW40WGpOUk1y?= =?utf-8?B?OUZNb0xJYkE4R1ZiMHBZbC9XK1B3VVA0YitOL0hxOWR6eHE4VVBleDVwQ2lU?= =?utf-8?B?ekw0YVRkaHJuMi83SHh6eGZraWZsWUNSbmx3bzhCTjg5UjY5Q1ZwMGRpTFh2?= =?utf-8?B?byswenVxd2MxZlFub0tWSXlYM1JGeDVFbWR3eWlrUm9CQjB2T0VyZnN6ZUFN?= =?utf-8?B?bk1ZbXY3a24vOEVvYXJnTHZoVjNGR3lxN0J1OWQ4Zk5CRHYrazNBeWx3SG8x?= =?utf-8?B?NVI3VHFkQVFSOU56WjF1K1VpNXU1YWV3aEhIS3ozZnYveW9oRWd2T1YxcnNy?= =?utf-8?B?bGxVNlAvY1hDMkl4dmFtZjVZbTM4czBBTnd5VkxtbzNyS1NHV2k3RWMyR01W?= =?utf-8?B?WVZONWJPWTlaRXdBbkQ0bXB0SmR0TWx5T09YMkVEYktNWkExVW5zSGlnMTIy?= =?utf-8?B?MWpnZXVwb1VzU29jaEdNTlZwc2U4eWRwTm5xTVRCaGpVR2hFdGxJYzFzaTZr?= =?utf-8?B?ZDFteWczZzFMQjN4L2VPNFp4YTFFLzhyS2xHV1p4YTBsQVM0YmtmMEtzaitY?= =?utf-8?B?NVd1bVpTUXpZN3ZXWkI2QkM2eFovUHlZdXIvL3VlQXVGSmNLYnhBWjJFRnVH?= =?utf-8?B?V2xkM0xqVDNSZllOTzFHQUZrbEluWUNnWTlaUHN5eXhZdFBocjhBd25YSkRn?= =?utf-8?B?dFhack9jcVp1a1lhcmlycHR6RjFRZzQwREpPRldyUWRDOU5MSXRjVDJWNkFX?= =?utf-8?B?dm9yYllMem1qUUtmdkFrbGlNV1ZXRE5JUGhRV3ZpRmNyeHhmRG5DVXBoYnZU?= =?utf-8?B?YTU3RWlWM3Z6cEVDSzlSRWg1a1h1dzRPUTh3cVZJUklhR2drUGJrMmVMZG8y?= =?utf-8?B?YStrU0VUNnJ1U3hiNlo1eGpKTUkxRkN2c0FCMjBiU1dHYlhQcW0rOHo0V1dI?= =?utf-8?B?MzRRRm5uQkFIN2lhQ2M3cEdWcVdQN3dPNElxTWdSYlFRaEc1MDRsbXcvRjNP?= =?utf-8?Q?CzJijgP4LunvYCOzGSKKVbo0I?= Content-Type: text/plain; charset="utf-8" Content-ID: <8E907FB35AF00B4FA0A65AB39163492B@namprd03.prod.outlook.com> Content-Transfer-Encoding: base64 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 X-OriginatorOrg: dartmouth.edu X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: DS7PR03MB5574.namprd03.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 8647cdd4-9f1c-4b65-289d-08dcc1edab19 X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Aug 2024 14:29:30.1573 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 995b0936-48d6-40e5-a31e-bf689ec9446f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: 46PW/LVmqjszeNqVpDg6LWkbzip1MCqE5uE4u4F4saXDCVGvd/c3hZYIcc40RuGQANSswpONyIawYMpKjQ25Mw== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR03MB5257 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.73 / 15.00]; MIME_BASE64_TEXT_BOGUS(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; ARC_ALLOW(-1.00)[microsoft.com:s=arcselector10001:i=1]; DMARC_POLICY_ALLOW(-0.50)[dartmouth.edu,none]; R_SPF_ALLOW(-0.20)[+ip6:2a01:111:f403::/49]; R_DKIM_ALLOW(-0.20)[dartmouth.edu:s=selector2]; NEURAL_SPAM_SHORT(0.16)[0.159]; MIME_GOOD(-0.10)[text/plain]; MIME_BASE64_TEXT(0.10)[]; XM_UA_NO_VERSION(0.01)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:8075, ipnet:2a01:111:f000::/36, country:US]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a01:111:f403:200a::70d:from]; TO_DN_EQ_ADDR_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[dartmouth.edu:+] X-Rspamd-Queue-Id: 4Wppcw5B0Gz4GLP SGkgYWxsLA0KDQpJIHBvc3RlZCBtZXNzYWdlcyB0byB0aGUgdGhpcyBsaXN0IGJhY2sgaW4gRmVi cnVhcnkgYW5kIE1hcmNoIA0KKGh0dHBzOi8vbGlzdHMuZnJlZWJzZC5vcmcvYXJjaGl2ZXMvZnJl ZWJzZC1jdXJyZW50LzIwMjQtRmVicnVhcnkvMDA1NTQ2Lmh0bWwpIA0KcmVnYXJkaW5nIGtlcm5l bCBwYW5pY3Mgd2Ugd2VyZSBoYXZpbmcgd2l0aCBuZnMgY2xpZW50cyBkb2luZyBoZGY1IGZpbGUg DQpvcGVyYXRpb25zLiBBZnRlciBhIGhpYXR1cyBpbiB0cm91Ymxlc2hvb3RpbmcsIEkgaGFkIG1v cmUgdGltZSB0aGlzIA0Kc3VtbWVyIGFuZCBoYXZlIGZvdW5kIHRoZSBjYXVzZSAtIHRoZSB2ZnMu bmZzZC5lbmFibGVfbG9jYWxsb2NrcyBzeXNjdGwuDQoNCldoZW4gdGhpcyBpcyBzZXQgdG8gMSwg d2UgY2FuIGluZHVjZSBlaXRoZXIgYSBwYW5pYyBvciBodW5nIG5mcyBzZXJ2ZXIgDQoobW9yZSBy YXJlbHkpIHVzdWFsbHkgd2l0aGluIGEgZmV3IGhvdXJzLCBidXQgc29tZXRpbWVzIHdpdGhpbiBz ZXZlcmFsIA0KZGF5cyB0byBhIHdlZWsuIFdlIGhhdmUgcmVwbGljYXRlZCB0aGlzIG9uIDEzLjAg dGhyb3VnaCAxNS4wLUNVUlJFTlQgDQooMjAyNDA3MjUtODIyODNjYWQxMmE0LTI3MTM2MCkuIFdp dGggdGhpcyBzZXQgdG8gMCAoZGVmYXVsdCksIHdlIGFyZSANCnVuYWJsZSB0byByZXBsaWNhdGUg dGhlIGlzc3VlLCBldmVuIGFmdGVyIHNldmVyYWwgd2Vla3Mgb2YgMjQvNyBoZGY1IA0KZmlsZSBv cGVyYXRpb25zLg0KDQpPbmUgb3RoZXIgc2lkZS1lZmZlY3Qgb2YgdGhlc2UgcGFuaWNzIGlzIHRo YXQgb24gYSBmZXcgb2NjYXNpb25zIGl0IGhhcyANCmNvcnJ1cHRlZCB0aGUgcm9vdCB6cG9vbCBi ZXlvbmQgcmVwYWlyLiBUaGlzIG1ha2VzIHNlbnNlIHNpbmNlIGtlcm5lbCANCm1lbW9yeSBpcyBn ZXR0aW5nIGNvcnJ1cHRlZCwgYnV0IG9idmlvdXNseSBtYWtlcyB0aGlzIGlzc3VlIG1vcmUgaW1w YWN0ZnVsLg0KDQpJJ20gaG9waW5nIHRoaXMgaXMgZW5vdWdoIGluZm9ybWF0aW9uIHRvIHN0YXJ0 IG5hcnJvd2luZyBkb3duIHRoaXMgDQppc3N1ZS4gV2UgYXJlIHNwZWNpZmljYWxseSB1c2luZyB0 aGlzIHN5c2N0bCBiZWNhdXNlIHdlIGFyZSBhbHNvIHNlcnZpbmcgDQpmaWxlcyB2aWEgc2FtYmEg YW5kIHdhbnQgdG8gZW5zdXJlIGNvbnNpc3RlbnQgbG9ja2luZy4NCg0KSSBoYXZlIHByb3ZpZGVk IHNvbWUgY29yZSBkdW1wcyBhbmQgYmFja3RyYWNlcyBwcmV2aW91c2x5LCBidXQgYW0gaGFwcHkg DQp0byBwcm92aWRlIG1vcmUgYXMgbmVlZGVkLiBJIGFsc28gaGF2ZSBhIHdyaXRldXAgb2YgZXhh Y3RseSBob3cgdG8gDQpyZXByb2R1Y2UgdGhpcyB0aGF0IEkgY2FuIHNlbmQgZGlyZWN0bHkgdG8g YW55b25lIHdobyBpcyBpbnRlcmVzdGVkLg0KDQpUaGFua3Mgc28gbXVjaCBmb3IgYW55IGFuZCBh bGwgaGVscCB3aXRoIHRoaXMgdHJpY2t5IHByb2JsZW0uIEknbSBoYXBweSANCnRvIGRvIHdoYXRl dmVyIEkgY2FuIHRvIGhlbHAgZ2V0IHRoaXMgc3F1YXNoZWQuDQoNCkJlc3QsDQpNYXR0DQo= From nobody Wed Aug 21 14:40:07 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WppsC6Gbkz5V0Cv for ; Wed, 21 Aug 2024 14:40:15 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WppsC5V8Xz4Hm3 for ; Wed, 21 Aug 2024 14:40:15 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724251215; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=0FHkM538hAxRUbzNoenbcYw9+F9jBjI2+fa/doONmJI=; b=xPqZ8hnQhq09abp3Y5eHVTFXJ5gAZ95tao1Mdz6xzEiDSEcpucMotkHDPIFGcnNFPnSATo mI1Edyzv0WlRXDyw3P5vnlOYUtvb/OMsMD0o24ikQJbWJNt2LP+J2qZ9tlDdp/GAkOS9+V +zI9VD7iznNOO3AQE+XQywd21cWJXjtLO6ZdPtdb135P5hbRsKgu90Q3jNiolCPhQ0jbhr fp1QV3x3Rzt7mbF2Wxetiymeu9J10+960q15CUFF3tZt5zJC64Mr7QnVQ/F3RMyvMQlf9m xkb5xVr9XE/MAr1UiRNqCn2YeAMeCYRFzC0nB1OUkW0esWkA1CV90AA8gD9MCw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724251215; a=rsa-sha256; cv=none; b=C3Jf/S+GtegfT4YoeA3bR+LfkAP9Ksxasdxtp2bULRbWpXfdSYg503CoEVhFe9q4+lzs0B h1dG/cecXFYB13U0XHKnxWYaf9CQUY4XSuaXU8wrqem0TE61JAAj/OBfrObuBX5J4TtByV U3JV7SXB2G7RfzCur9Vq0dMWpkjYqJwD9cpOLc6aZx27wB327NKg870Zs5ih8X0Z7rpsjP Zbjsjs2oRuSDYjqgpmLYEbiDU2lqQ832ooTtUm1uO1QnNOK1+XD+KOTGsAJBinoZ1/kWll GplkugvDmTcIcnkbvA6uPFgkGd9ipUeELoKB99MKr0Uew57k4jlGlLegUBBQHg== ARC-Authentication-Results: i=1; thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724251215; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: dkim-signature; bh=0FHkM538hAxRUbzNoenbcYw9+F9jBjI2+fa/doONmJI=; b=ugcZ/GeKx+qy5LqiDvpL2QRlVknjkjnWentIK16ZdZu/ztI8qybZZ/5kfEnDzKyuDFBmkM YwX/trIaVle9fGZnug08nZs6WhPGcrsKARL9UHbBroxO0yFpmtVVJeHjHUL1X7588si/9Y UXTy+1MvNIem7CSKnuHoWs7zMY9b34VJ0joC+6vA7hFCM4HvfYQOBkjWrs3kAJmSCsRGTT LQErXWmFmcfdGkbV5Vl08cn+A5R2QN4SNzN/ONjhwLpDSSSssDa/KKmur3Ch4KjxvZi9Xy Izgmwe6J1MhBm0ixwMm8HPggiANY6RIcstB5Y5nCCwu6pGSnRWZdXO776Mqq/Q== Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.lerctr.org", Issuer "R10" (verified OK)) (Authenticated sender: ler/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4WppsC4ylnzZVx for ; Wed, 21 Aug 2024 14:40:15 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=ler2019; h=Content-Type:Message-ID:Subject:To:From:Date:MIME-Version:Sender :Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description; bh=0FHkM538hAxRUbzNoenbcYw9+F9jBjI2+fa/doONmJI=; b=E4EjlH5AhB/soHPsvbsWnxOqxV 3DFYRkLdiUzIcrIXSzAm+GjjBQ2h8eFyWPrWZtLDrwrM/fb+zFmEsOWAmU+JH9Ev46e86t5RE1Rbd Jf0nGHizoxGlMhsJ0t2roYwzVuZAy0taH1+ULqnTLdfLpRrmVp0MX2JkZUMBmLE0z7SN8sKnOxQ3d uT1o+/+e7sMPtzzzINv/5jeYmfvauBAz/K2eb/wDYV3NhGcvCR/vfeagRQ1DsIdcLLImRMwmiSPvB c4nIiUEXuRrcHlQvA/X12EhLZRkgE0UgeOzvEhtKXi6XC6uULggll15voYhnTTGzc6Y18/jE8BBU+ SVjmOL2g==; Authentication-Results: thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none Received-SPF: softfail (thebighonker.lerctr.org: transitioning domain of FreeBSD.org does not designate 192.147.25.65 as permitted sender) client-ip=192.147.25.65; envelope-from=ler@FreeBSD.org; helo=webmail.lerctr.org; Received: from thebighonker.lerctr.org ([192.147.25.65]:43503 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.98 (FreeBSD)) (envelope-from ) id 1sgmVI-00000000Nji-3RWI for freebsd-current@freebsd.org; Wed, 21 Aug 2024 09:40:10 -0500 Received: from syn-070-123-041-087.res.spectrum.com ([70.123.41.87]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Wed, 21 Aug 2024 09:40:07 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Date: Wed, 21 Aug 2024 09:40:07 -0500 From: Larry Rosenman To: Freebsd current Subject: Missing Drivers? Message-ID: X-Sender: ler@FreeBSD.org Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_3e0f43a3efda5d4b5afe2b893d99de0e"; micalg=pgp-sha256 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_3e0f43a3efda5d4b5afe2b893d99de0e Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Any chance of getting Bluetooth working on this box and/or any other missing pieces? dmesg.boot: https://www.lerctr.org/~ler/ryzen/dmesg.boot pciconf -lv: https://www.lerctr.org/~ler/ryzen/pciconf.txt Thanks1 -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 --=_3e0f43a3efda5d4b5afe2b893d99de0e Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=488 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEHjgknedhWzvJgwVzaXyZsatIp30FAmbF/EoACgkQaXyZsatI p310Tgf/X54ldbQPZ2VtPzKOtr1a28dVTkxoT8waBHsvMmGzV1NTm8keh3iqnart DzR/CnhfWksu8ZYUnSXc1Q+c5ZVLxjM8CqBL5+T24Qq0nKl5C36VOsHKdDRcdbys KeRt62JKqMtrr8V1Katx+iAgAAOWZHYVDVovPxpNC17ibSLa4/fmT0gBlM4DPMvN AxmBwhi6kVrQbw7iUh71nL0UUq/gTjM9dcXglZFwxgAMnHs6CJzTHr8nWIEmUMIN edYVgUBHjYLR9WqIH8vvvg0chL/WxgWWgtPhuFf57O+x8/vCCbXJugH1xbLPn36d yu+nLSmyO+2hDOS0fWMw42sQeL6emQ== =ukfo -----END PGP SIGNATURE----- --=_3e0f43a3efda5d4b5afe2b893d99de0e-- From nobody Wed Aug 21 14:45:31 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WppzW3njrz5V0LK for ; Wed, 21 Aug 2024 14:45:43 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WppzW25cgz4Jq9 for ; Wed, 21 Aug 2024 14:45:43 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x530.google.com with SMTP id 41be03b00d2f7-656d8b346d2so3989846a12.2 for ; Wed, 21 Aug 2024 07:45:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724251542; x=1724856342; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZxvJ8xMhaVCajf4JEkGK8K5zDzXri/JsiHJwbuIOgUQ=; b=SexOk49UBTJfoZa5dJx85E1YwFCofO93RxdgtAnK4fA8XvtGABDue9DwS3w2oLd+rr CAIvBr2JJNjWfEDdIPmWLhi4+3mh/O60DueZfQ3biGqlpxA/vOo6Xr4h6lqOrXWrVW9g CzxXE/fx3reqlWyL99iVZii+yObiKFDK/Kj6K0bsk9Zif70UcLwWAh2NFnGjTYc1JANV p+VcBtJlkeFjO0lWxq+KpWaB14WEjQETQaPx9sU9GkMHVlcrBPMKrIbL2/3SikAkBz9Z kAM/TJa2DrwSugP+XNij8AGDelFbuaO/EtrstqTuyRo7dAzhAP/41Qe3WARhLWRJNozu v4Ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724251542; x=1724856342; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ZxvJ8xMhaVCajf4JEkGK8K5zDzXri/JsiHJwbuIOgUQ=; b=pEBznvQbeICFeKIVCUoHvbNYAR8n96mq4A4+9qETW8j6jPLsnI+vTlZhOOAMTT3zSO FZP7jQLhHUeCWqP2nQB37PH7UNnIon43lI6taLWzsXArocV76pO/259BJSg0alMEHyev xrGEl9GvRARbIPLrqsNCAqhmxHPEXcCYeR880+Kl3zZ/oqxaekkmD7B0dch9oQz++yQq zTkanBw2dNqBIjRnZ6sz6gT2mSHneNQTDepqzHyJsh3hzFiEAR5geBIt7bSGuf1zh+XL 699qiaHNfYYTcZZAqPKZ/Ca/I1Z2ranbdEQfAopvPa87FFga+oIDLO5gPut0kt+EgrQd TtvQ== X-Gm-Message-State: AOJu0YyWYc/jAdfEZ3rXFt95dgXP2b9C8qnqn9RigpD10YtSnqhUaRdY XEZEL3mis22bEhuMG1rrf7G8rVIMDJitWYQE1C5lxwVyAbOuMfHPUSnhbH8uEDaThvevHGRD8IL FbgzpFdopVpfskxw8UYO3eNMRCQ== X-Google-Smtp-Source: AGHT+IHhD1U4u/OveiN8Smiz2F4bVFwS9mRww+cN828shBmU5arM5FO8X2md76sm8cpBsfs7ZqczWGndAa58uJWatD4= X-Received: by 2002:a05:6a21:3983:b0:1c0:e1a5:9583 with SMTP id adf61e73a8af0-1cad810c8b2mr3192759637.17.1724251541580; Wed, 21 Aug 2024 07:45:41 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <3ed15b15-6f1c-4290-a552-aaafef7cc82e@dartmouth.edu> In-Reply-To: <3ed15b15-6f1c-4290-a552-aaafef7cc82e@dartmouth.edu> From: Rick Macklem Date: Wed, 21 Aug 2024 07:45:31 -0700 Message-ID: Subject: Re: Kernel panics with vfs.nfsd.enable_locallocks=1 and nfs clients doing hdf5 file operations To: "Matthew L. Dailey" Cc: "freebsd-current@freebsd.org" Content-Type: multipart/alternative; boundary="000000000000a3b8890620329877" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4WppzW25cgz4Jq9 --000000000000a3b8890620329877 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Please create a PR for this and include at least one backtrace. I will try and figure out how locallocks could cause it. I suspect few use locallocks=3D1. rick On Wed, Aug 21, 2024 at 7:29=E2=80=AFAM Matthew L. Dailey < Matthew.L.Dailey@dartmouth.edu> wrote: > Hi all, > > I posted messages to the this list back in February and March > ( > https://lists.freebsd.org/archives/freebsd-current/2024-February/005546.h= tml) > > regarding kernel panics we were having with nfs clients doing hdf5 file > operations. After a hiatus in troubleshooting, I had more time this > summer and have found the cause - the vfs.nfsd.enable_locallocks sysctl. > > When this is set to 1, we can induce either a panic or hung nfs server > (more rarely) usually within a few hours, but sometimes within several > days to a week. We have replicated this on 13.0 through 15.0-CURRENT > (20240725-82283cad12a4-271360). With this set to 0 (default), we are > unable to replicate the issue, even after several weeks of 24/7 hdf5 > file operations. > > One other side-effect of these panics is that on a few occasions it has > corrupted the root zpool beyond repair. This makes sense since kernel > memory is getting corrupted, but obviously makes this issue more impactfu= l. > > I'm hoping this is enough information to start narrowing down this > issue. We are specifically using this sysctl because we are also serving > files via samba and want to ensure consistent locking. > > I have provided some core dumps and backtraces previously, but am happy > to provide more as needed. I also have a writeup of exactly how to > reproduce this that I can send directly to anyone who is interested. > > Thanks so much for any and all help with this tricky problem. I'm happy > to do whatever I can to help get this squashed. > > Best, > Matt > --000000000000a3b8890620329877 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Please create a PR for this and include at least
one backtrace. I will try and fi= gure out how
locallocks could cause it.

I suspect few use locallocks=3D1.

rick

On Wed, Aug 21, 2024 at 7:= 29=E2=80=AFAM Matthew L. Dailey <Matthew.L.Dailey@dartmouth.edu> wrote:
Hi all,

I posted messages to the this list back in February and March
(https://lists.freebsd.o= rg/archives/freebsd-current/2024-February/005546.html)
regarding kernel panics we were having with nfs clients doing hdf5 file operations. After a hiatus in troubleshooting, I had more time this
summer and have found the cause - the vfs.nfsd.enable_locallocks sysctl.
When this is set to 1, we can induce either a panic or hung nfs server
(more rarely) usually within a few hours, but sometimes within several
days to a week. We have replicated this on 13.0 through 15.0-CURRENT
(20240725-82283cad12a4-271360). With this set to 0 (default), we are
unable to replicate the issue, even after several weeks of 24/7 hdf5
file operations.

One other side-effect of these panics is that on a few occasions it has corrupted the root zpool beyond repair. This makes sense since kernel
memory is getting corrupted, but obviously makes this issue more impactful.=

I'm hoping this is enough information to start narrowing down this
issue. We are specifically using this sysctl because we are also serving files via samba and want to ensure consistent locking.

I have provided some core dumps and backtraces previously, but am happy to provide more as needed. I also have a writeup of exactly how to
reproduce this that I can send directly to anyone who is interested.

Thanks so much for any and all help with this tricky problem. I'm happy=
to do whatever I can to help get this squashed.

Best,
Matt
--000000000000a3b8890620329877-- From nobody Wed Aug 21 15:02:28 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WpqLw595Qz5V1br for ; Wed, 21 Aug 2024 15:02:32 +0000 (UTC) (envelope-from Matthew.L.Dailey@dartmouth.edu) Received: from CY4PR05CU001.outbound.protection.outlook.com (mail-westcentralusazlp170100000.outbound.protection.outlook.com [IPv6:2a01:111:f403:c112::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "DigiCert Cloud Services CA-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WpqLv6Yxnz4M72 for ; Wed, 21 Aug 2024 15:02:31 +0000 (UTC) (envelope-from Matthew.L.Dailey@dartmouth.edu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=dartmouth.edu header.s=selector2 header.b=GWKqo9Ia; dmarc=pass (policy=none) header.from=dartmouth.edu; spf=pass (mx1.freebsd.org: domain of Matthew.L.Dailey@dartmouth.edu designates 2a01:111:f403:c112:: as permitted sender) smtp.mailfrom=Matthew.L.Dailey@dartmouth.edu; arc=pass ("microsoft.com:s=arcselector10001:i=1") ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=CzvkHzzcQRFSMR1veB4Z2FS4Ajg5LcK1FJ0kmkw7t5HZB3q/lqNXsWFUWuq454meaCsfiCjarDlf/63sO18DT2Q0pgiTiXoWqH4A0C7M1pAN3ObYnn/6MxA8oAhBYvxtr6VmhPGn/XO+bcSAbipRTzLcwhlJ/b9P9eoBqTZsrfIiOJuJ3qO7/gx1o6/3xFufB2bwtrKytajbF75AaOUqxVL1XiZGV8Oh9XXyAoAJXW0VN2DHrzVy/O9PpaXcrVaftfgtQMGUX4BFCePGkL4fDYzDvsUZf9iqg4ZXTOakJX3mcN9hWc2/TaskpTiBrJOwP0Qqd7SW309yF0CLQ9EnuQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=aAvnhDzxNRS5k7xm3gAa9M9hSSNmKF1geU7Yk6hR1Sc=; b=EY7Hw5Twu4O1+zDKs7m2KASBKKGhOtLHELZRBtHAbUgH9yRzlwX3a5YkX9jWjNPzPxqS6mig/TMaAU3RkYN//5UVuLebf0AOPyARbKQAC2r80rei69cgXM/efvIXm9Fc3JNd8m6z511QQvBxLJIKuMVBtkMtVVP2TPYAuAgZNp64XeXeQRvup7hAxp5d4SWWRNrCy+JwQeZEtAZp6jkWMEC1X3KjRlcL5o6cW5QRMdUwmPUj0PnqgGqe65xGKH+BWv6z5cf0CJGpx8HwV3yNSXRv1b12Ly3NuZJGh5g7AksWne3AGireU7/JMZNNnLLBU3i56EFW0E8rG/4VZEjqHg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=dartmouth.edu; dmarc=pass action=none header.from=dartmouth.edu; dkim=pass header.d=dartmouth.edu; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dartmouth.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aAvnhDzxNRS5k7xm3gAa9M9hSSNmKF1geU7Yk6hR1Sc=; b=GWKqo9IaocbNDh+dfNVyXGft9dAR/bQfOrJkel6An7ScGgiPqpxgxtw1N9TyVVxF77uIQyHQPjcPnMKKvzGv+RBsBbMFlvvfmyTpLbqFh9oQxvjuAJ4uZAj4OJvABbmZjdoDM5hN2Q9NjbbbabEsXqKgh8fY9reGimgmumJFyg4= Received: from DS7PR03MB5574.namprd03.prod.outlook.com (2603:10b6:5:2c1::16) by CH0PR03MB5953.namprd03.prod.outlook.com (2603:10b6:610:e0::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7897.19; Wed, 21 Aug 2024 15:02:28 +0000 Received: from DS7PR03MB5574.namprd03.prod.outlook.com ([fe80::5340:c731:1512:51d7]) by DS7PR03MB5574.namprd03.prod.outlook.com ([fe80::5340:c731:1512:51d7%7]) with mapi id 15.20.7897.014; Wed, 21 Aug 2024 15:02:28 +0000 From: "Matthew L. Dailey" To: Rick Macklem CC: "freebsd-current@freebsd.org" Subject: Re: Kernel panics with vfs.nfsd.enable_locallocks=1 and nfs clients doing hdf5 file operations Thread-Topic: Kernel panics with vfs.nfsd.enable_locallocks=1 and nfs clients doing hdf5 file operations Thread-Index: AQHa89sjKFIwgCfGJkm6+Gxxahmh7Q== Date: Wed, 21 Aug 2024 15:02:28 +0000 Message-ID: <43c2f01e-c1b4-493d-8187-11e16d1da851@dartmouth.edu> References: <3ed15b15-6f1c-4290-a552-aaafef7cc82e@dartmouth.edu> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla Thunderbird x-ms-publictraffictype: Email x-ms-traffictypediagnostic: DS7PR03MB5574:EE_|CH0PR03MB5953:EE_ x-ms-office365-filtering-correlation-id: 94379e38-a4bf-47f1-e092-08dcc1f2467d x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0;ARA:13230040|366016|376014|1800799024|38070700018; x-microsoft-antispam-message-info: =?utf-8?B?M29XTmZPOGpNTWc2R3JaUGI4WFdlMGdaZUFPekl2RzRyMytua3hvZ2VZYzJs?= =?utf-8?B?Q1dUaFJoa3crWnBCQ0Q3RlYwZVFrRVVnM2FEb21CQnN4VExRQi9QQ0RPRXNZ?= =?utf-8?B?amhWZTJWbzFvS2lHVnNxcWI1Vnh1ZmlQQlZuYWh1SnlWSXluRy96Y1NWZ0R4?= =?utf-8?B?RmhhVlRFNjhhR1J0UWE2a3o2bDF5cE5RK3BkTDVwYW9oNzJmSjd0KzlUWXFR?= =?utf-8?B?WmJOUDBiYm9WczZ5dFZkbDlKNWp2UkZEQjJLTTZvbnRZSE9lekY5U1Yva0Ur?= =?utf-8?B?dGo3M0ZMeXNLL1E0TWg2dnpXcit0LzVPV1duc1pkVG9QSGlQS1o2TW9VRCt2?= =?utf-8?B?bDg3ZlpUa1V1N0NGdDI3U2JXajM4UDdkRUF0ZnZWdG44MmhpaUJZM0pPa2xQ?= =?utf-8?B?Z2pUcXJ5TVJFY0pubVMyWjFEdjRzSGc4UGxTSVV1SHIwRk5kTFNGY2lWdXpZ?= =?utf-8?B?QnFVQjVVeWViL0h6V2F1dGdUNU1oUkExTEVTNXBJbUdrWklGWlFneFNlaWdV?= =?utf-8?B?ODdLOUxrNWo1eHNvNmxxajBGc1lLei9mbkhsNkNQTWE1QkpSakFLR0VTdm1E?= =?utf-8?B?WnZlU0NmK1JLYitKcDEzVUQybGZncDIrN2tTM2dIcUdKV29ZRVo4aXA5djRV?= =?utf-8?B?VDRXb0N5Q1FxTWRiUkhMcEFCamtkbGU5RG1QY2JpMDFGNzU2NjcyWmZjUWkx?= =?utf-8?B?Vkp0L2N3cGxEZ25TNExCUE5ybGpld3NQbzMrWS9OVG9tc2lYVjVoS3E0WkZm?= =?utf-8?B?RHo0VTVUVS9uT3NDNXgxVlBuZEZwMDgyU3ZzN1Y3NFFJbm0xdEdqdGhhYW5U?= =?utf-8?B?RVI1bUh3M09ZZ1NxOUtQNnpQc1E3RytHbmxlTVRoNXJpVmhWV0NMQ2djSFJU?= =?utf-8?B?Mm5NZXRlQ3p4dWFtVDZxd0t2Kzh0Y3N5eFUxYzdWN2JaK0w3b3dWZ2Z5LzUv?= =?utf-8?B?Q0NDSjQrUWk3clEzeUtRKzN0Tm1yUm5ZWkdERjY2TEtveHdNVTlya254cFhK?= =?utf-8?B?ZGNTZTZMYWtSS1JqeWFkSEZnSExJdGd1ZGJGR0dYL2ZodmN2UjBJdkFXRHNE?= =?utf-8?B?MzkvRzNISmwycEVNdGozeUNEeEg4dVQzalpiaTdUNEl2RTJpZUxKamMvSkhy?= =?utf-8?B?R2FmZXZ2S01YWkhMSHhMdW5vLzRjM3ozYU02akdLRzFiVnl1dmhaTjk1UWVU?= =?utf-8?B?TzlGZEJWVjJOdnpkcFg0Yis3SVVJdFdyU3k0MTh2bmN4VHVEVUpmQng3MmtQ?= =?utf-8?B?cmFYc1FweTlLWDdpdlJkYUprWE1USHN2a0ZJSHc3L0RRMHBzeXFaeXV2V1Fl?= =?utf-8?B?MnpFYWtYSit1OElTRGJJWHljYUVwZUhWY2JoR0lKNXE2OVVhZml6aFRmQ3NQ?= =?utf-8?B?cWVmV0VyVXI5L2ZGaVRsNTdUNzBUL01CdzUxWkc4bEdzOEZzU3YzSUtGTVB3?= =?utf-8?B?Y08vanpYQUdYUis0YjBGL2RBTHpZOTc3dll3S0dEaXFxbk03Z1pZQkpzV2JF?= =?utf-8?B?b2d3eDhNYktJM3FmODRSMGdDWE1NczJBcVlLejFyMkhXTG1ESUR3YjhkWTdQ?= =?utf-8?B?dVpXK3hhUlo5V09OeWF6dzJNcmd3OExHOFF2Q2hIRXNhaTk1bjdsU0NBSTFX?= =?utf-8?B?U1d1bktpaFNJRTFZMGVqaXJ5dW5mSWFVYVlHa21ERG5xYmdlOTZnMFFxVkNT?= =?utf-8?B?b3VSbHVqVU03S0NDMTg5K0ZHR09lR2xjVTF5eUowcHNYbGNJbE1UVWxNMjF5?= =?utf-8?B?MSsxbUhld2U0K2lpSEhTTU9rSlFHWnlnYWJDakkzVFNzN0ZVLzMwNHlzT2ZC?= =?utf-8?Q?xQwSrJ8hVe4+voxUPT0bYuovMrtWLW3nhkeEU=3D?= x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DS7PR03MB5574.namprd03.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(366016)(376014)(1800799024)(38070700018);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?utf-8?B?alk1RjBrakg5ZEVEZmpET0VjRVljWDRDTS9TQm80bWZUWTkrVFo0bk5BRmlK?= =?utf-8?B?TERZbmdzbnpTVnBydzh1cE8zSnB1WnNWcVo4eGdMcHdPbW5UUzJWZ2l3dEhu?= =?utf-8?B?MTMrYURUeDBMYzRwSGxWVEw2VHFmdENlK2t4dUlQVnA3R0tuS3RUZnhSLzhE?= =?utf-8?B?Q3BRTk5HZWVTL3doZGRGd1hMckMxN3F2UmZ6V0M2U0dxNEVmLzlJRWJnNUlG?= =?utf-8?B?RlVteFVtWGxXWEY4ckNmUWxUc0JmdXpqSTZhdGdYOTBqQWlqaUFlYWI5UTBS?= =?utf-8?B?SDd5VHBJeFBTTiszVDQ5c0FXTzRKM0F6Yjc5ajBTTXRLb1A4TnVqbmp1SUdq?= =?utf-8?B?RHBrRDFSSGZyK2lwOW5JT2dTaXZQeVFueDdyRE9SRG5jVm5KV1ppVS8rZTA0?= =?utf-8?B?LzN6WEFqeUNCbkd4N3VrQis3UkVRSWZ2OUxMdGhpOVdQY0g1Y2l2OEo4N01h?= =?utf-8?B?MnVheTRKUWpCMGVUS0VnUEV3WnBHTVVoQVd0QzNBb1JQRWQ0ZDFsL2QzbURE?= =?utf-8?B?cS9IVk44M2ZMbUtFSlVyMGZRUGRseXRhOTFOL3kwU2E3SVN5RzlQWllmYVF5?= =?utf-8?B?UGZ4emlhTjh0QWx6R0lucFpINUFESlRtRjRORVhtUEQ2U09mRjhDeXNQSS9Q?= =?utf-8?B?Yldtak04bktLc2hxUUZuaGpCMzBnVWY4V1lWcStLaXVwTHJlUFdvNW83ZzZr?= =?utf-8?B?eUJxeFRLb28zM3JDRHA3ZktKc25reHZLYjhOdUFqTVE4cEJlZDFNcTlyTGF6?= =?utf-8?B?ZzJWRGlzaUhWaXFOZHFhN1drZXlWTVhEbGhETmhoNU9HQ3gzdkdYaXNKcWRz?= =?utf-8?B?MjRRZW5WbzVNWXplWmRYNC9yWUJXUWpxOWVHWE8vUnREYmpCN3dtTjdGYjVk?= =?utf-8?B?NFVraTFtMlJ0eDlwWnhPTTF4a3FvTlQ2VldXUitBS21PRUxIWnBnSGdxdnIx?= =?utf-8?B?TjNlTU15ay9HRHhmOW5UcEpHdkpqZUFhbGxDTlVLc3JwblNvSVh4YTgzQVlv?= =?utf-8?B?M0t3ZW1ZWFBKa3pua2YrRFZEblpBSlRNQnZlUW51emtiVnNkYmo3MWdtS2l4?= =?utf-8?B?OXBMZjVLcnREME9GNk82RXdEcnJReGRYVS9WZE9qb05ncTB6bGhCRUFmY1VK?= =?utf-8?B?d3JscWpidGVKWGgvVUdHRzBOYit4S2d5d0hSNWU4N2JYQ0IxUFlFRnhvUytO?= =?utf-8?B?Z3FRQjU0SCtDZ0pwZzJudjhOTVpZOUxtZ3h1RHRJck1tK2d2TnY4TG9iQTlY?= =?utf-8?B?R09MU3RBNWYrRzNpZWU3dWk2MVh5aTlFbVM4dTlNRDJHa0tIdEQwa0FOcy9K?= =?utf-8?B?b1RGV3Z1RzZJUlJRb2tnL0YrV0FTQ2poa2xxclpjbW8vdFFMbkVoYXM4OHFo?= =?utf-8?B?R3BXT0kyeHltNEo5VlBSRVl3K0hDRTdmVUd2dFZ6d2pocUpQVTM5enNOenQw?= =?utf-8?B?c3N6S0kxNmdNUmJXRlBtYjZjdUs3R3d0WURkTWJoTndlaGY5d0p4R2d0UkRB?= =?utf-8?B?ZFhxMXhTUVJqRCsxKzB1dXhhNHRCRkhRNExBOFNYeTNRUlR6K2x4cTR3OW9P?= =?utf-8?B?NU5wQjRITHdKMFFpODBNNU5seTI3c2N2dzdaeWhKVCtFQ0YzMEFmLzhVYm0w?= =?utf-8?B?Sll1WktVdFZUbW51dTRDeEJUYUVVM2VJaHR4eHg3Sk5WTUo4TnlUV3Q1MENH?= =?utf-8?B?ZUcyRVFLL0c4U3J2V3lIdGxpYjdNbUFiY0h5d09tZHlkcGZaSFdtVW1nb2Fk?= =?utf-8?B?UFFtQmdiQ2xsVW9PM0lDZmVUMXdVRWpFV1hOekxveEJkU2V1dXREZkZ3VElS?= =?utf-8?B?WXRVR1NiQkxOYS94RjBTb0ZaeXp2dGhrUldSMzQwaStYYTJYT0d6eUF5cGc4?= =?utf-8?B?WGFwd2VzR3NrZnRwMGQwOHJZVndnWVJTU3VWcDBYZEViV2NZSE9jdlFRNTFS?= =?utf-8?B?U2pZNU9tRys0QkVadUdnUXlYaE5BLzI5ekZGRGxrbko5VUpzd1FQUHVHT1Q2?= =?utf-8?B?TUpJTFdSSVhLSHJTRmcyanJKZ3YrWGFnTm1FL1RKOG5pWE9aeitzcUp5cVBJ?= =?utf-8?B?bXBzNno3RmJCZjJHdXFUY1NyemRoQytuckRDME9BVCtsWTJpR2ttdHdJVi92?= =?utf-8?Q?+No5HL4316uvdXHNyj/x2C3dd?= Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 X-OriginatorOrg: dartmouth.edu X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: DS7PR03MB5574.namprd03.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 94379e38-a4bf-47f1-e092-08dcc1f2467d X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Aug 2024 15:02:28.8290 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 995b0936-48d6-40e5-a31e-bf689ec9446f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: /OWnEHdWOf4wSw8jhvZ/3Gon/Zsat1SPI1NsY0LDg15H9aKAw9iFf8XzwDESN81xh400srHSE2IvlCOdSxq6KA== X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH0PR03MB5953 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.82 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; ARC_ALLOW(-1.00)[microsoft.com:s=arcselector10001:i=1]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.93)[-0.931]; DMARC_POLICY_ALLOW(-0.50)[dartmouth.edu,none]; R_DKIM_ALLOW(-0.20)[dartmouth.edu:s=selector2]; R_SPF_ALLOW(-0.20)[+ip6:2a01:111:f403:c000::/51]; MIME_BASE64_TEXT(0.10)[]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; TAGGED_RCPT(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_SOME(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; ASN(0.00)[asn:8075, ipnet:2a01:111:f000::/36, country:US]; RCPT_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[dartmouth.edu:+] X-Rspamd-Queue-Id: 4WpqLv6Yxnz4M72 SGkgUmljaywNCg0KRG9uZSAtIGh0dHBzOi8vYnVncy5mcmVlYnNkLm9yZy9idWd6aWxsYS9zaG93 X2J1Zy5jZ2k/aWQ9MjgwOTc4DQoNClRoYW5rcyENCg0KLU1hdHQNCg0KT24gOC8yMS8yNCAxMDo0 NSBBTSwgUmljayBNYWNrbGVtIHdyb3RlOg0KPiBQbGVhc2UgY3JlYXRlIGEgUFIgZm9yIHRoaXMg YW5kIGluY2x1ZGUgYXQgbGVhc3QNCj4gb25lIGJhY2t0cmFjZS4gSSB3aWxsIHRyeSBhbmQgZmln dXJlIG91dCBob3cNCj4gbG9jYWxsb2NrcyBjb3VsZCBjYXVzZSBpdC4NCj4gDQo+IEkgc3VzcGVj dCBmZXcgdXNlIGxvY2FsbG9ja3M9MS4NCj4gDQo+IHJpY2sNCj4gDQo+IE9uIFdlZCwgQXVnIDIx LCAyMDI0IGF0IDc6MjnigK9BTSBNYXR0aGV3IEwuIERhaWxleSANCj4gPE1hdHRoZXcuTC5EYWls ZXlAZGFydG1vdXRoLmVkdSA8bWFpbHRvOk1hdHRoZXcuTC5EYWlsZXlAZGFydG1vdXRoLmVkdT4+ IA0KPiB3cm90ZToNCj4gDQo+ICAgICBIaSBhbGwsDQo+IA0KPiAgICAgSSBwb3N0ZWQgbWVzc2Fn ZXMgdG8gdGhlIHRoaXMgbGlzdCBiYWNrIGluIEZlYnJ1YXJ5IGFuZCBNYXJjaA0KPiAgICAgKGh0 dHBzOi8vbGlzdHMuZnJlZWJzZC5vcmcvYXJjaGl2ZXMvZnJlZWJzZC1jdXJyZW50LzIwMjQtRmVi cnVhcnkvMDA1NTQ2Lmh0bWwgPGh0dHBzOi8vbGlzdHMuZnJlZWJzZC5vcmcvYXJjaGl2ZXMvZnJl ZWJzZC1jdXJyZW50LzIwMjQtRmVicnVhcnkvMDA1NTQ2Lmh0bWw+KQ0KPiAgICAgcmVnYXJkaW5n IGtlcm5lbCBwYW5pY3Mgd2Ugd2VyZSBoYXZpbmcgd2l0aCBuZnMgY2xpZW50cyBkb2luZyBoZGY1 IGZpbGUNCj4gICAgIG9wZXJhdGlvbnMuIEFmdGVyIGEgaGlhdHVzIGluIHRyb3VibGVzaG9vdGlu ZywgSSBoYWQgbW9yZSB0aW1lIHRoaXMNCj4gICAgIHN1bW1lciBhbmQgaGF2ZSBmb3VuZCB0aGUg Y2F1c2UgLSB0aGUgdmZzLm5mc2QuZW5hYmxlX2xvY2FsbG9ja3Mgc3lzY3RsLg0KPiANCj4gICAg IFdoZW4gdGhpcyBpcyBzZXQgdG8gMSwgd2UgY2FuIGluZHVjZSBlaXRoZXIgYSBwYW5pYyBvciBo dW5nIG5mcyBzZXJ2ZXINCj4gICAgIChtb3JlIHJhcmVseSkgdXN1YWxseSB3aXRoaW4gYSBmZXcg aG91cnMsIGJ1dCBzb21ldGltZXMgd2l0aGluIHNldmVyYWwNCj4gICAgIGRheXMgdG8gYSB3ZWVr LiBXZSBoYXZlIHJlcGxpY2F0ZWQgdGhpcyBvbiAxMy4wIHRocm91Z2ggMTUuMC1DVVJSRU5UDQo+ ICAgICAoMjAyNDA3MjUtODIyODNjYWQxMmE0LTI3MTM2MCkuIFdpdGggdGhpcyBzZXQgdG8gMCAo ZGVmYXVsdCksIHdlIGFyZQ0KPiAgICAgdW5hYmxlIHRvIHJlcGxpY2F0ZSB0aGUgaXNzdWUsIGV2 ZW4gYWZ0ZXIgc2V2ZXJhbCB3ZWVrcyBvZiAyNC83IGhkZjUNCj4gICAgIGZpbGUgb3BlcmF0aW9u cy4NCj4gDQo+ICAgICBPbmUgb3RoZXIgc2lkZS1lZmZlY3Qgb2YgdGhlc2UgcGFuaWNzIGlzIHRo YXQgb24gYSBmZXcgb2NjYXNpb25zIGl0IGhhcw0KPiAgICAgY29ycnVwdGVkIHRoZSByb290IHpw b29sIGJleW9uZCByZXBhaXIuIFRoaXMgbWFrZXMgc2Vuc2Ugc2luY2Uga2VybmVsDQo+ICAgICBt ZW1vcnkgaXMgZ2V0dGluZyBjb3JydXB0ZWQsIGJ1dCBvYnZpb3VzbHkgbWFrZXMgdGhpcyBpc3N1 ZSBtb3JlDQo+ICAgICBpbXBhY3RmdWwuDQo+IA0KPiAgICAgSSdtIGhvcGluZyB0aGlzIGlzIGVu b3VnaCBpbmZvcm1hdGlvbiB0byBzdGFydCBuYXJyb3dpbmcgZG93biB0aGlzDQo+ICAgICBpc3N1 ZS4gV2UgYXJlIHNwZWNpZmljYWxseSB1c2luZyB0aGlzIHN5c2N0bCBiZWNhdXNlIHdlIGFyZSBh bHNvDQo+ICAgICBzZXJ2aW5nDQo+ICAgICBmaWxlcyB2aWEgc2FtYmEgYW5kIHdhbnQgdG8gZW5z dXJlIGNvbnNpc3RlbnQgbG9ja2luZy4NCj4gDQo+ICAgICBJIGhhdmUgcHJvdmlkZWQgc29tZSBj b3JlIGR1bXBzIGFuZCBiYWNrdHJhY2VzIHByZXZpb3VzbHksIGJ1dCBhbSBoYXBweQ0KPiAgICAg dG8gcHJvdmlkZSBtb3JlIGFzIG5lZWRlZC4gSSBhbHNvIGhhdmUgYSB3cml0ZXVwIG9mIGV4YWN0 bHkgaG93IHRvDQo+ICAgICByZXByb2R1Y2UgdGhpcyB0aGF0IEkgY2FuIHNlbmQgZGlyZWN0bHkg dG8gYW55b25lIHdobyBpcyBpbnRlcmVzdGVkLg0KPiANCj4gICAgIFRoYW5rcyBzbyBtdWNoIGZv ciBhbnkgYW5kIGFsbCBoZWxwIHdpdGggdGhpcyB0cmlja3kgcHJvYmxlbS4gSSdtIGhhcHB5DQo+ ICAgICB0byBkbyB3aGF0ZXZlciBJIGNhbiB0byBoZWxwIGdldCB0aGlzIHNxdWFzaGVkLg0KPiAN Cj4gICAgIEJlc3QsDQo+ICAgICBNYXR0DQo+IA0K From nobody Sat Aug 24 17:06:21 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wrjyb6N3jz5TSJG for ; Sat, 24 Aug 2024 17:06:31 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WrjyZ4bf4z4Jrb for ; Sat, 24 Aug 2024 17:06:29 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of phk@critter.freebsd.dk designates 130.225.244.222 as permitted sender) smtp.mailfrom=phk@critter.freebsd.dk Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 8A181892B6 for ; Sat, 24 Aug 2024 17:06:21 +0000 (UTC) Received: (from phk@localhost) by critter.freebsd.dk (8.18.1/8.16.1/Submit) id 47OH6LfG023651; Sat, 24 Aug 2024 17:06:21 GMT (envelope-from phk) Message-Id: <202408241706.47OH6LfG023651@critter.freebsd.dk> To: current@freebsd.org Subject: powerd forgets top CPU frequency ? From: Poul-Henning Kamp List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <23649.1724519181.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Sat, 24 Aug 2024 17:06:21 +0000 X-Spamd-Bar: - X-Spamd-Result: default: False [-1.99 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.986]; FORGED_SENDER(0.30)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[phk]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_NEQ_ENVFROM(0.00)[phk@phk.freebsd.dk,phk@critter.freebsd.dk]; R_DKIM_NA(0.00)[]; DMARC_NA(0.00)[freebsd.dk]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[current@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4WrjyZ4bf4z4Jrb On T14s thinkpad running: FreeBSD critter.freebsd.dk 15.0-CURRENT FreeBSD 15.0-CURRENT #7 main-n271= 455-a1740cb93639-dirty: Thu Aug 1 09:45:40 UTC 2024 root@critter.free= bsd.dk:/critter/obj/critter/FreeBSD/src/amd64.amd64/sys/GENERIC-NODEBUG am= d64 When I run two 100% CPU loaded processes, the machine gradually gets slowe= r and slower, until eventually it limps along at 500-ish MHz rates. Killing powerd and starting it again seems to bring the machine back to fu= ll speed (for some time). Looking at the powerd -v output, my gut feeling is that powerd sometimes l= ooses track of what the (current) top frequency is and thus gradually drag= s the machine slower or slower... I have had a faint feeling for some time that this machine runs significan= tly faster after a reboot, but I have no observations to support that. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence= . From nobody Sat Aug 24 19:14:09 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wrmnx68gSz5Tg4s for ; Sat, 24 Aug 2024 19:14:13 +0000 (UTC) (envelope-from gbe@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wrmnx5YVPz4Y8Q for ; Sat, 24 Aug 2024 19:14:13 +0000 (UTC) (envelope-from gbe@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724526853; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=m5dxWMLuwjeBeRaRu2zqN9or8HSXJ7rvXBEyHURht2U=; b=D+FO/yY5KWZ6YMh0zP4UCZT4q+jt+n3tCkTmE4vw0UCWSp+1l8iCeeRS5yccsW8Fh1+Lie HCHXNczp2xM3LVJrgzUfUlqU5lc+u1630+3sd0FGRw6cV7mrBIX/DmbebqeMrDfF2AdcaL uPFHU+a1fzj4mdFDnb0Hi83ZmEYwE8jUaLl8PWRkjFAoQe2IbZDU9APWImmiPuvZ8I9VlW lU+2zQl40V76E574Dqzoii5rd6YpRQ6z2o+vtPL5n7DnmUEJHU1FFMQic1b2KIGxfIeBDO 9VS5KEDFRRh0uZnwFDm07cs7g+6qvEBr6TQ+9Ndb0fLsWTG8MDRa/iGMsatj2A== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724526853; a=rsa-sha256; cv=none; b=DkAOlMFpNq4Ye33s4IgEghHUiMVaaJ2YvOEMchbnfwRuMiSq/8nXt7ocslEVqS2eDJ9LAz JWzYiDniMtYYB8JvxuifwPi1tLqepc0EpcJcKztR1S6cOUuqYnUm69hsmssE+mztewTdcr xcC8vFlAsc8DpDEkiJZnBQ3RxwRZajCSNFndGyvODZb5fl75Yb0ZSQIbmTq1az8Vc+bXju +3O8oqJHBB2GUgAqNH0d/NAV9rOV1won7NZ5fhUEUBw9ZlsUak3SUymDhUgm7NkEfodHJg tbOMU+NyD8aMsUgT4WkVxjunGVX64Sh+Fi8xMj5107EoePX8gXU45Wr7NOAjKQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724526853; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=m5dxWMLuwjeBeRaRu2zqN9or8HSXJ7rvXBEyHURht2U=; b=ujq6Jg8Ei/SmqJkhcAHXHNHg0lWsKYhKtM3aCsxoBePC08O8cHRBfDlCvtMcQJaBpXntLk mjuRPRIr8VXetIPilBPtYcw8qvmM5XBrzScTocnwKW+j6Sc27IQaU6PIf+cURVLZnl1KQB t1fXQ9JVUfpq5eqwrKhNXbUj2HEtVMFqaZd9caazZVsGh7sPEpfirGEMqAEhD3WZhXwOU0 zvb62F2/xCMV61NNrGoJ6MPwy1dTIDZL0v7l6knjAmy3AJ95asy9mqeU7GKA9GjduoBkWG 3BCfINJPCs3zqktd7QXDAu8bAw+e91zGqpCe3LkB7fTYdoMvvrHhzpxbkdyBNg== Received: from localhost (p200300cb871c2d935950e660ca2827d7.dip0.t-ipconnect.de [IPv6:2003:cb:871c:2d93:5950:e660:ca28:27d7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: gbe) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Wrmnx22y3z1BPT for ; Sat, 24 Aug 2024 19:14:13 +0000 (UTC) (envelope-from gbe@freebsd.org) Date: Sat, 24 Aug 2024 21:14:09 +0200 From: Gordon Bergling To: freebsd-current@freebsd.org Subject: buildworld error Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="8mq/qOkN/bXKmGy8" Content-Disposition: inline X-Url: X-Operating-System: FreeBSD 14.1-RELEASE-p3 amd64 X-Host-Uptime: 9:10PM up 10 days, 16:51, 3 users, load averages: 0.15, 0.20, 0.17 --8mq/qOkN/bXKmGy8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi folks, I got the following buildworld error a recent -CURRENT ===> stand/i386/pxeldr (all) `kldstat.o' is up to date. -14152 bytes available The same happens on stable/14: ===> stand/i386/pxeldr (all) -22344 bytes available ===> share/misc (all) --- loader --- *** [loader] Error code 1 make[5]: stopped in /storage/freebsd/src/stable/14/stand/i386/pxeldr 1 error src.conf looks like the following: WITH_BEARSSL=1 WITH_RETPOLINE=1 WITHOUT_CLEAN=1 I remove the whole obj directories and tried several full builds, but the error persists for a while. Has any one a clue how to solve this? --Gordon --8mq/qOkN/bXKmGy8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEYbWI0KY5X7yH/Fy4OQX2V8rP09wFAmbKMP8ACgkQOQX2V8rP 09y1KwgAhhy17VEWnV6Feb8gDGC8crx0NaTU1M6QBb3PuU4xKDnt+OrGeTaes8rT gu21rhSxUZ9/DSdw8dyYbHC4AbiUQ7vNREJEpWR0Hi/KZ12W4FT9ogt3bT2RSkAz tbDbrNFf43FbY/cWwrf/MLjBIwvz2a/WsGOIcaZsotHCZetMfbFpIaoplAsRXJo2 EhNGmuNfXXkjGY2tj9DIwxLJMSNfg/lmZiXZjrCsrHGJzgIRtFaHg7kqtddQpIde hsSvNC4cJJcZXzPKZYu0yBzN2w+RutveQks8n1YlyA/N3lOzFFLvwsPqNrGeXYix CuAVqQcQLkJJ5j9xnsBCBH5HB1fV5Q== =uWze -----END PGP SIGNATURE----- --8mq/qOkN/bXKmGy8-- From nobody Sat Aug 24 19:29:55 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wrn8K6Cclz5Th07 for ; Sat, 24 Aug 2024 19:30:09 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wrn8J67Nfz4Zwd for ; Sat, 24 Aug 2024 19:30:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ot1-x330.google.com with SMTP id 46e09a7af769-709339c91f9so2485875a34.0 for ; Sat, 24 Aug 2024 12:30:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1724527807; x=1725132607; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=yFVzB8GCoR2sP+M0o3tEsoPPqQYqyZ0zFUSghUK4Fbk=; b=vYRPcqIF7Oi4odS7u7IuH2shmk3uEf+rSiaQ8cjfM+ohO0Yz/QDHWNMoy06MgiBKJz +fVuB9G7A3dzZWXu90qPgPngjtoywFnpIHXE+2BGnZY4quwOCKU65gC30zySnuAXJtw8 OssI/7Y9FnUQLlZaSzu6M/fkfNnHkySKeLBxToCwW6SjEjiyZnKdzMOqbQIwc1vix5HY ZGPN9uBK4i6TkjYF33a8z8+Dp72uEuAYtvan88kdbQArsHezOKdqQ7LCyC12iYpmX+Vx QTKyriZb7+LfFq+dM9DsGjTTPRwPTQJa/DgI2TsZQYyKlO2NauqmQWZ1bHcvRH04KtJi 2JSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724527807; x=1725132607; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=yFVzB8GCoR2sP+M0o3tEsoPPqQYqyZ0zFUSghUK4Fbk=; b=mY37nqmqfyQzDhZirb2kYpN/vJvPooUg5ezsGRq5qABKCb5vEKcRO30SH+M0Xq8Z0a 7Fsus/c58tMltW9+nOrkjtCl5xCV0p+p2RHFWQZgies0bNnMh2fCluDUdrk1sh8J19Op PYf9n6AKy71zx+O8V4unHrxn2pbM66qPcXnaL3VZRVvmpGq/Me9A4Kkh/K27Nz2Racwr EwDJkCwA+Q5Mc9fIk3MPTFxQdeeBD0RdkOu+XoTIap83qz2Tp+KKFITWUFbmXrkJfG0m juY1rbjELauVZ/zj6u44UhjJSxb1SMq5YI6AfUAToeBThS/PL8YkfVkAjZRS6gQZO34i grYQ== X-Gm-Message-State: AOJu0YyiPBAXjYgnaP4dxTe5yzsn5DW2hGLbgD6XDNFH34MzE1Cc1lfd Cioy57f/UzKO2HsSHbVqAtb1AbQfxtiiuEOe+8U0N4RdbzLyc/IFZ0/qCtisjBrr1B6N0iiv+QO ekhQBYRqg1aEhbp32vyc6kNW2paNF7G9YmHXSBA== X-Google-Smtp-Source: AGHT+IEOy+Ds7HpTjf4XH1APIYFu6cAwALV6+bgPF6/MYjNiweGoBtGHb6MGsIMd6MhLwPwWKNb6oenr+lSS0dDRLVw= X-Received: by 2002:a05:6830:600f:b0:709:5cda:5d19 with SMTP id 46e09a7af769-70e0ebfa01amr8900373a34.27.1724527806774; Sat, 24 Aug 2024 12:30:06 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sat, 24 Aug 2024 13:29:55 -0600 Message-ID: Subject: Re: buildworld error To: Gordon Bergling Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000054183f062072ebd7" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Wrn8J67Nfz4Zwd --00000000000054183f062072ebd7 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Aug 24, 2024, 1:14=E2=80=AFPM Gordon Bergling wro= te: > Hi folks, > > I got the following buildworld error a recent -CURRENT > > =3D=3D=3D> stand/i386/pxeldr (all) > `kldstat.o' is up to date. > -14152 bytes available > > The same happens on stable/14: > > =3D=3D=3D> stand/i386/pxeldr (all) > -22344 bytes available > =3D=3D=3D> share/misc (all) > --- loader --- > *** [loader] Error code 1 > > make[5]: stopped in /storage/freebsd/src/stable/14/stand/i386/pxeldr > 1 error > > src.conf looks like the following: > WITH_BEARSSL=3D1 > WITH_RETPOLINE=3D1 > WITHOUT_CLEAN=3D1 > > I remove the whole obj directories and tried several full builds, but the > error persists for a while. > > Has any one a clue how to solve this? Either disable pxe, raise the pxe limit (though it may not work), or select the 4th loader for pxeboot. The loader is too big on BIOS to enable all the options. Warner --Gordon > --00000000000054183f062072ebd7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Aug 24, 2024, 1:14=E2=80=AFPM Gordon Bergling = <gbe@freebsd.org> wrote:
Hi folks,

I got the following buildworld error a recent -CURRENT

=3D=3D=3D> stand/i386/pxeldr (all)
`kldstat.o' is up to date.
-14152 bytes available

The same happens on stable/14:

=3D=3D=3D> stand/i386/pxeldr (all)
-22344 bytes available
=3D=3D=3D> share/misc (all)
--- loader ---
*** [loader] Error code 1

make[5]: stopped in /storage/freebsd/src/stable/14/stand/i386/pxeldr
1 error

src.conf looks like the following:
WITH_BEARSSL=3D1
WITH_RETPOLINE=3D1
WITHOUT_CLEAN=3D1

I remove the whole obj directories and tried several full builds, but the error persists for a while.

Has any one a clue how to solve this?

Either disable pxe, raise the pxe limit (t= hough it may not work), or select the 4th loader for pxeboot.

The loader is= too big on BIOS to enable all the options.

Warner

--Gordon
--00000000000054183f062072ebd7-- From nobody Sat Aug 24 19:39:28 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WrnM53zqMz5Thn4 for ; Sat, 24 Aug 2024 19:39:29 +0000 (UTC) (envelope-from gbe@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WrnM537mpz4d7k; Sat, 24 Aug 2024 19:39:29 +0000 (UTC) (envelope-from gbe@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724528369; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WvuBqyrBfQA3dTd/KsGC1BLnOxc4mSOf5oe05J9AgCs=; b=j96O/fRLv65ThhKaUgLDkh8UG4Vp97rHckIcKZg+yxZFdoSmAy4MhZ8S7zXIciDhQU3YQ3 qGWnZll6J+if3FVaA7OGx8bYOf06a9RmvF9wjLdyQAkCRXV+pb83Pm4gyQ+RrGz0JBXfDz J7HXqeRO1/dzhbmNzSLYYWAoHG+K5wCHX2yHbTXSCkjDdFGpQFvIDeicAzFLDtJukeji4p ixthm19mMbBunDaNoQxzeylZCmSzbUaQI0ep/7dKaSRUB12TXwadlsWyX0DuRsvpaDtU98 g2jroHCEdo+8HLst/TIH9o7awMmzkr0UDdk4oOdcABJryDpRXUnEN+XHy7yjOw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724528369; a=rsa-sha256; cv=none; b=Yv77fNcmH+D0Ox4Tg1EplfTbxIr0T1vsiXmYeq4YzC98/Q+CMZ95mJTrrJWI6igR/1b/xq qrDjwEm/XXKtsk9EbqARjYZaR0XAWrV/FIQ6mUNLsPA2lhLKfxVINWBgJDG1kE+sKWndL8 yb7JqLtLpZeMT0zm0LzMs/csy4VAxCUfrKOtNQQAWl5WXABH6nPvn4Vs4Y28w1dPeIAJzd ZuAuHj+//wwKj0rsDEp1bXxZdsAd2pkezSYlW+8roZOu8GTA8gRMkl9xBR5BGl4aWSrzN/ /bp1ssWiXNpjQAgHsBRcxMBQj+gEZ9JhS7hekx67wG0dDZl3KKfPTjfK4A31/w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724528369; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WvuBqyrBfQA3dTd/KsGC1BLnOxc4mSOf5oe05J9AgCs=; b=Um07Ang6X2nSUETBJgz7lfWqdh21bqKa8ii/ofGqrYCpJKWr/mQPMzqWO1zFTCfg+h/p+m YpmTZTtDJqJ0IjhOMVvYitC+GVVok0/jC43ODOdLzmtn+X4elUaavGRtRJPd303wurt4nC MB9mEQLfp4uwj8xqfQvxwjt5OTQVxJWHP2TVhRXiniZpCwDYe5Qs9SMgKKezYu6FLb0KeW WJrBtbGnIB8FBmvkfyIdMpu1tfksb7SK222lT4e0shqwL3N9MRPiE4gwjMtV8h6pQv8OVB amOlU+Zcii2to33d0uJRvystFn5/Hd7G9cmePG5+9WpNVKU1LGDBcxONF7wL4A== Received: from localhost (p200300cb871c2d935950e660ca2827d7.dip0.t-ipconnect.de [IPv6:2003:cb:871c:2d93:5950:e660:ca28:27d7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: gbe) by smtp.freebsd.org (Postfix) with ESMTPSA id 4WrnM46Zlsz19SP; Sat, 24 Aug 2024 19:39:28 +0000 (UTC) (envelope-from gbe@freebsd.org) Date: Sat, 24 Aug 2024 21:39:28 +0200 From: Gordon Bergling To: Warner Losh Cc: FreeBSD Current Subject: Re: buildworld error Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Url: X-Operating-System: FreeBSD 14.1-RELEASE-p3 amd64 X-Host-Uptime: 9:34PM up 10 days, 17:15, 3 users, load averages: 0.21, 0.20, 0.17 Hi Warner, On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote: > On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling wrote: > > I got the following buildworld error a recent -CURRENT > > > > ===> stand/i386/pxeldr (all) > > `kldstat.o' is up to date. > > -14152 bytes available > > > > The same happens on stable/14: > > > > ===> stand/i386/pxeldr (all) > > -22344 bytes available > > ===> share/misc (all) > > --- loader --- > > *** [loader] Error code 1 > > > > make[5]: stopped in /storage/freebsd/src/stable/14/stand/i386/pxeldr > > 1 error > > > > src.conf looks like the following: > > WITH_BEARSSL=1 > > WITH_RETPOLINE=1 > > WITHOUT_CLEAN=1 > > > > I remove the whole obj directories and tried several full builds, but the > > error persists for a while. > > > > Has any one a clue how to solve this? > > Either disable pxe, raise the pxe limit (though it may not work), or select > the 4th loader for pxeboot. > > The loader is too big on BIOS to enable all the options. I looked at src.conf(5), but didn't found a switch to disable pxe. What I am wondering about is that no one is facing the problem, since this it is a pretty clean build without and special modifications, despite the ones mention above in the src.conf. Did you have a hint on how to disable pxe? --Gordon From nobody Sat Aug 24 19:56:11 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WrnkT2dKcz5Tjxm for ; Sat, 24 Aug 2024 19:56:17 +0000 (UTC) (envelope-from concussious@runbox.com) Received: from mailtransmit05.runbox.com (mailtransmit05.runbox.com [IPv6:2a0c:5a00:149::26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WrnkR5jDGz4gkC for ; Sat, 24 Aug 2024 19:56:15 +0000 (UTC) (envelope-from concussious@runbox.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=runbox.com header.s=selector1 header.b=3ebjAvIQ; dmarc=pass (policy=quarantine) header.from=runbox.com; spf=pass (mx1.freebsd.org: domain of concussious@runbox.com designates 2a0c:5a00:149::26 as permitted sender) smtp.mailfrom=concussious@runbox.com Received: from mailtransmit03.runbox ([10.9.9.163] helo=aibo.runbox.com) by mailtransmit05.runbox.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1shwrr-008Awa-Fs for freebsd-current@freebsd.org; Sat, 24 Aug 2024 21:56:11 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=runbox.com; s=selector1; h=Message-Id:Date:Subject:To:From:MIME-Version: Content-Transfer-Encoding:Content-Type; bh=JrLIig52exhBY5tC3FkvDR4CRQNjYkL9rh3WmJfJdYE=; b=3ebjAvIQvJrePUH5Gcy/W5RGMr cdZvCkwZGr6ZW4+tx29B2fbzukzX/YXmmnX51xRxwG7zOBx0hs6a71KUB7zqWc70lB+z08oxoWnbd OC6RxtDVWLvwK2UjyRIm2eCdizMx4/dDCpv5klG8V/KGnzDQ8vViVv/B6PwNq0x7q+vYXBciUrHfU 3iGtlBsEmFSrQxiIofZDEiX0GfNL59LNAzRbJDvJbKBWReWAmrkGEHtPkGXPIcrFkS0Tk78NIZBOG KiHMSqw+FLV/VLdiHRe7KxOOOhAKamf4GoVSpogy2/xQZQL0dfyi4JBj4hCHgKYt3813aq7nzGEbZ +daeS3GQ==; Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1shwrr-0003Jv-5s for freebsd-current@freebsd.org; Sat, 24 Aug 2024 21:56:11 +0200 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1shwrr-0005DB-4j for freebsd-current@freebsd.org; Sat, 24 Aug 2024 21:56:11 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Received: from [Authenticated alias (960610)] by runbox.com with http (RMM6); for ; Sat, 24 Aug 2024 19:56:11 GMT From: "Alexander Ziaee" To: "freebsd-current" Subject: GENERIC boot hangs on `enabling pf` Date: Sat, 24 Aug 2024 19:56:11 +0000 (UTC) X-RMM-Aliasid: 960610 X-Mailer: RMM6 Message-Id: X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.09 / 15.00]; DWL_DNSWL_LOW(-1.00)[runbox.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.990]; DMARC_POLICY_ALLOW(-0.50)[runbox.com,quarantine]; R_SPF_ALLOW(-0.20)[+ip6:2a0c:5a00:149::26]; R_DKIM_ALLOW(-0.20)[runbox.com:s=selector1]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[2a0c:5a00:149::26:from]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:50304, ipnet:2a0c:5a00::/29, country:NO]; FREEMAIL_FROM(0.00)[runbox.com]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[runbox.com]; ARC_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_THREE(0.00)[4]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[runbox.com:+] X-Rspamd-Queue-Id: 4WrnkR5jDGz4gkC Hi everyone, On a new laptop GENERIC sometimes hangs on `enabling pf`. When it does, ctr= l-alt-del or the power button will begin power off, but hangs on `uhub0:det= ached` after `uptime: 6m39s`. Sometimes it does this multiple boots in a ro= w. Usually at least once out of every ten times. My old laptop doesn't ever do this. It takes 14hrs to makeworld and dies ra= ndomly so I only try to update it during stabilization week (<3 for stabili= zation week). This is my hobby laptop for working on freebsd, so it is available for any = and all testing that may be helpful, but I don't know where to begin with t= his type of issue. Best, Alex= From nobody Sat Aug 24 20:10:13 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wrp2j5C4hz5TlD2 for ; Sat, 24 Aug 2024 20:10:21 +0000 (UTC) (envelope-from SRS0=nd1y=PX=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wrp2j2y9lz4j9M for ; Sat, 24 Aug 2024 20:10:21 +0000 (UTC) (envelope-from SRS0=nd1y=PX=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Sat, 24 Aug 2024 22:10:13 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1724530213; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=H1/wrW5L3pMpzzPpdg0jkMRn2UtF1z2BdcoODFMnuNw=; b=sC2/aGGMYoJwK4umW4rxkAZd1pJXuxoLhGar0eLNDkSD20KN+gQHKIdN47SM9ldh5l1MxK 4yE6AUy7f/XiKM5RwbS2436Cg7lGccGw6cncB7EDWOHTKeq63C0cijNJIGZH6pTkvwtg+n +4NSa5cGfJog5tH28VS6ffCPPBI7nRljvgTzzYshdn1+FSqSMucnhj8iWtx8RiLQUbaDjm bxN3RxyVZTChqQ07PI90Kw2c3jyyOAhGCq9VAFHTOXgsbe+nXKvarld3f1qsKbgSm4hCeV QAQZVeyLH3AK42r5iiHLyoJTZ+GJ/dLsHYXO3n0tF3XaWEyb909q2i0O6uXLRg== From: Ronald Klop To: Alexander Ziaee Cc: freebsd-current Message-ID: <220348662.12939.1724530213477@localhost> In-Reply-To: Subject: Re: GENERIC boot hangs on `enabling pf` List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_12938_2013145627.1724530213470" X-Mailer: Realworks (717.35) Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Queue-Id: 4Wrp2j2y9lz4j9M ------=_Part_12938_2013145627.1724530213470 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Alexander Ziaee Datum: 24 augustus 2024 21:56 Aan: freebsd-current Onderwerp: GENERIC boot hangs on `enabling pf` > > > Hi everyone, > > On a new laptop GENERIC sometimes hangs on `enabling pf`. When it does, ctrl-alt-del or the power button will begin power off, but hangs on `uhub0:detached` after `uptime: 6m39s`. Sometimes it does this multiple boots in a row. Usually at least once out of every ten times. > > My old laptop doesn't ever do this. It takes 14hrs to makeworld and dies randomly so I only try to update it during stabilization week (<3 for stabilization week). > > This is my hobby laptop for working on freebsd, so it is available for any and all testing that may be helpful, but I don't know where to begin with this type of issue. > > Best, > Alex > > > > What version of freebsd? Do you have a pf config? If it hangs what does ctrl-t output? Regards, Ronald ------=_Part_12938_2013145627.1724530213470 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

Van: Alexander Ziaee <concussious@runbox.com>
Datum: 24 augustus 2024 21:56
Aan: freebsd-current <freebsd-current@freebsd.org>
Onderwerp: GENERIC boot hangs on `enabling pf`

Hi everyone,

On a new laptop GENERIC sometimes hangs on `enabling pf`. When it does, ctrl-alt-del or the power button will begin power off, but hangs on `uhub0:detached` after `uptime: 6m39s`. Sometimes it does this multiple boots in a row. Usually at least once out of every ten times.

My old laptop doesn't ever do this. It takes 14hrs to makeworld and dies randomly so I only try to update it during stabilization week (<3 for stabilization week).

This is my hobby laptop for working on freebsd, so it is available for any and all testing that may be helpful, but I don't know where to begin with this type of issue.

Best,
Alex

What version of freebsd?
Do you have a pf config?
If it hangs what does ctrl-t output?

Regards,
Ronald

------=_Part_12938_2013145627.1724530213470-- From nobody Sat Aug 24 21:21:16 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wrqcn2VdRz5Tbrp for ; Sat, 24 Aug 2024 21:21:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wrqcm6sywz4qVg for ; Sat, 24 Aug 2024 21:21:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ot1-x331.google.com with SMTP id 46e09a7af769-70940c9657dso2396323a34.1 for ; Sat, 24 Aug 2024 14:21:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1724534488; x=1725139288; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=NC3uVwldgZ6PpUi8zjVTNqKNEBPfQ6qY3U33iDoQr2s=; b=JNLcug9cIXuyy39Cup8BqI2jPFlqijD29TgQlvaswZjTfZ6BOTwRgibrjJFrE07Qey DWmwhPPGSE42wyFsfYGTMj0X75a1UfJ2CrRp3U2Dpaw16Di8ea9cnhVxrDvCG3sZ1+pB C4PB5VELR/Jc49QRt1pDr4cBdkofuR26mnvMmjBGzSx3U2D7OsyK/HldJirFdwXLjejk PQDP1cvT3JChz9I37QOpui9Nz4xaCyyjxz+mqZV4X7GgplJp5907acRtyic81EVpQfgc hwtP+c7i8J17xXHjArviMblhmWGPgS6fRaHniz1bBhI50eP8QDDffyuzr4Cg0Zr7mz2V uHuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724534488; x=1725139288; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=NC3uVwldgZ6PpUi8zjVTNqKNEBPfQ6qY3U33iDoQr2s=; b=kJz0jwMhEDUP1dwuEbnrJAr8irh5CE1aIonjh2RNR57NAuxIyCohOzVfKdBjJc37md JBKlJTHg2DjXJdmo/6+nhAgCoG31F/5L8XWqY/QqJKK04DztqQxFCxhAGCQmPGa5LuEV uE19aqgwLBri5plsuy4eQ0iWDPJzDl2t7mbMLOHRJOE+qqrDV3asSAn62Nd7U8ogqcQX fwaUvCJrN4TfmVbLgmbbiBftTK3tCb6V1nEFmXjdzbZVu75pHJ0anVNVMoeRlljGPR5a BK2Hk02/TzpQrT09C0dOmLV6/v7xlgGBexM/J82QtmQLNTH7uWcTFunQT/i951lCi/d9 bVVA== X-Gm-Message-State: AOJu0YyHzhmG1P9B1AoTREoE4ZJni2o1ffgrMFhGQKmzchTH9fzzpSbd d/TELBMf6h0JLauJv59cMqq2Yhn7culJ0BkWeyHGu9FHfJlA7jZaN7ogZiY9lQ1pCuPQl9Onlqj ua/X4xxUBxaObA/sUYQtLaFC5hz+TZFTM3TJlUakoT/ptl60D+0c= X-Google-Smtp-Source: AGHT+IEog2opZh47YE9/SigBZfCJOfGVhCpTUk/UNi4mLcxnLBCmhDTUQwboxvzNOstw+WFsWH+rFiwwvL8hM9nnZkQ= X-Received: by 2002:a05:6830:90c:b0:708:b3c0:1442 with SMTP id 46e09a7af769-70e0eadf77cmr6095567a34.1.1724534487623; Sat, 24 Aug 2024 14:21:27 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sat, 24 Aug 2024 15:21:16 -0600 Message-ID: Subject: Re: buildworld error To: Gordon Bergling Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000089c080062074797c" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Wrqcm6sywz4qVg --00000000000089c080062074797c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Aug 24, 2024 at 1:39=E2=80=AFPM Gordon Bergling w= rote: > Hi Warner, > > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote: > > On Sat, Aug 24, 2024, 1:14=E2=80=AFPM Gordon Bergling = wrote: > > > I got the following buildworld error a recent -CURRENT > > > > > > =3D=3D=3D> stand/i386/pxeldr (all) > > > `kldstat.o' is up to date. > > > -14152 bytes available > > > > > > The same happens on stable/14: > > > > > > =3D=3D=3D> stand/i386/pxeldr (all) > > > -22344 bytes available > > > =3D=3D=3D> share/misc (all) > > > --- loader --- > > > *** [loader] Error code 1 > > > > > > make[5]: stopped in /storage/freebsd/src/stable/14/stand/i386/pxeldr > > > 1 error > > > > > > src.conf looks like the following: > > > WITH_BEARSSL=3D1 > > > WITH_RETPOLINE=3D1 > > > WITHOUT_CLEAN=3D1 > > > > > > I remove the whole obj directories and tried several full builds, but > the > > > error persists for a while. > > > > > > Has any one a clue how to solve this? > > > > Either disable pxe, raise the pxe limit (though it may not work), or > select > > the 4th loader for pxeboot. > > > > The loader is too big on BIOS to enable all the options. > > I looked at src.conf(5), but didn't found a switch to disable pxe. What I > am > wondering about is that no one is facing the problem, since this it is a > pretty clean build without and special modifications, despite the ones > mention > above in the src.conf. > > Did you have a hint on how to disable pxe? > I was sure that I'd documented everything, but it seems not: WITHOUT_LOADER_PXEBOOT=3Dt PXEBOOT_DEFAULT_INTERP=3D4th PXEBOOTSIZE?=3D525000 I'll look to make sure I don't have a commit stuck in a branch somewhere...= . Warner --00000000000089c080062074797c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Aug 24, 2024 at 1:39=E2=80=AF= PM Gordon Bergling <gbe@freebsd.org> wrote:
Hi= Warner,

On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote:
> On Sat, Aug 24, 2024, 1:14=E2=80=AFPM Gordon Bergling <gbe@freebsd.org> wrote:
> > I got the following buildworld error a recent -CURRENT
> >
> > =3D=3D=3D> stand/i386/pxeldr (all)
> > `kldstat.o' is up to date.
> > -14152 bytes available
> >
> > The same happens on stable/14:
> >
> > =3D=3D=3D> stand/i386/pxeldr (all)
> > -22344 bytes available
> > =3D=3D=3D> share/misc (all)
> > --- loader ---
> > *** [loader] Error code 1
> >
> > make[5]: stopped in /storage/freebsd/src/stable/14/stand/i386/pxe= ldr
> > 1 error
> >
> > src.conf looks like the following:
> > WITH_BEARSSL=3D1
> > WITH_RETPOLINE=3D1
> > WITHOUT_CLEAN=3D1
> >
> > I remove the whole obj directories and tried several full builds,= but the
> > error persists for a while.
> >
> > Has any one a clue how to solve this?
>
> Either disable pxe, raise the pxe limit (though it may not work), or s= elect
> the 4th loader for pxeboot.
>
> The loader is too big on BIOS to enable all the options.

I looked at src.conf(5), but didn't found a switch to disable pxe. What= I am
wondering about is that no one is facing the problem, since this it is a pretty clean build without and special modifications, despite the ones ment= ion
above in the src.conf.

Did you have a hint on how to disable pxe?

<= div>I was sure that I'd documented everything, but it seems not:
<= div>
WITHOUT_LOADER_PXEBOOT=3Dt
PXEBOOT_DEFAULT_INT= ERP=3D4th
PXEBOOTSIZE?=3D525000

= I'll look to make sure I don't have a commit stuck in a branch some= where....

Warner
--00000000000089c080062074797c-- From nobody Sat Aug 24 23:12:13 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Wrt515Rtzz5TmQY for ; Sat, 24 Aug 2024 23:12:37 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from gid2.gid.co.uk (ns0.gid.co.uk [IPv6:2001:470:94de::240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gid2.gid.co.uk", Issuer "gid2.gid.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Wrt512b8gz4253 for ; Sat, 24 Aug 2024 23:12:37 +0000 (UTC) (envelope-from rb@gid.co.uk) Authentication-Results: mx1.freebsd.org; none Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by gid2.gid.co.uk (8.15.2/8.15.2) with ESMTP id 47ONCS83074048; Sun, 25 Aug 2024 00:12:28 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from smtpclient.apple (moriarty.gid.co.uk [194.32.164.17]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id 47ONCNAr084498; Sun, 25 Aug 2024 00:12:23 +0100 (BST) (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=utf-8 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\)) Subject: Re: powerd forgets top CPU frequency ? From: Bob Bishop In-Reply-To: <202408241706.47OH6LfG023651@critter.freebsd.dk> Date: Sun, 25 Aug 2024 00:12:13 +0100 Cc: "current@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <202408241706.47OH6LfG023651@critter.freebsd.dk> To: Poul-Henning Kamp X-Mailer: Apple Mail (2.3774.600.62) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Queue-Id: 4Wrt512b8gz4253 Hi, > On 24 Aug 2024, at 18:06, Poul-Henning Kamp = wrote: >=20 > On T14s thinkpad running: >=20 > FreeBSD critter.freebsd.dk 15.0-CURRENT FreeBSD 15.0-CURRENT #7 = main-n271455-a1740cb93639-dirty: Thu Aug 1 09:45:40 UTC 2024 = root@critter.freebsd.dk:/critter/obj/critter/FreeBSD/src/amd64.amd64/sys/G= ENERIC-NODEBUG amd64 >=20 > When I run two 100% CPU loaded processes, the machine gradually gets = slower and slower, until eventually it limps along at 500-ish MHz rates. >=20 > Killing powerd and starting it again seems to bring the machine back = to full speed (for some time). >=20 > Looking at the powerd -v output, my gut feeling is that powerd = sometimes looses track of what the (current) top frequency is and thus = gradually drags the machine slower or slower... Possibly buggy ACPI on the Thinkpad not reporting any frequency higher = than it=E2=80=99s actually running at? > I have had a faint feeling for some time that this machine runs = significantly faster after a reboot, but I have no observations to = support that. >=20 > --=20 > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by = incompetence. -- Bob Bishop rb@gid.co.uk From nobody Sat Aug 24 23:33:41 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WrtYS2bVtz5TpH4 for ; Sat, 24 Aug 2024 23:33:48 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WrtYS1kJtz43VK for ; Sat, 24 Aug 2024 23:33:48 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724542428; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=unO/x9iA49MT6dTsa9kuPTwBviCMe7odiMKI7yTyolU=; b=W+6eKHJm6MkBCBAnlYsRJYIfGK+QSTt8uJXCjvlNBIh/9zWB9UFLnP2uTzYDU/Vj2AHrAU SiNJT0qO/jRQYmPe3tGC8Kzqsf4l0UYMLybhNbtG8c1OuI+CLtT4jQHTDGVI1kLhxmRBLe uQwwcCI5T+/tpowpZdh+azESQMElOqZq6R8DyzJ75TRSiWuvq146aSew4w4/rJHDS3592e k30rYZzyMmgRrHjkeSkOi7MO1bcQyocFKwE7vPh34Hpuluoi0glmkAWvPI+BzlIUj75gtv rgoB1sRfToCMI8MJ7PDU50q6JYGwnI93K3ABtmpqR7j8SJIsZn7B3Ik98ronig== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724542428; a=rsa-sha256; cv=none; b=gxOIeifEtZvrZ2ULy499wZlQy7SrkYgCYo9mARCe8MOaFMyjAXF2zjNcxhzIRsihGJHjU2 z30moKyl1F73/o9vWRgv3HcDOa3KPVqIzRNujCAtbMeXLyZSeinteHaFHNiwuDGVt8p2UM ePg3SSn+yeTMHGRk+oP09f2FYMepg/e2S+YAzKpsFh5VzCQhE0KEY/14OK23kNhG37C3AQ 71qGfh1Icn8DGMqSZYtharO2obhpkTrjR3myrX/1Y6otXYEOE4ykHRvmimm9/yjYNfFV/8 dYdOcs9lnAYWX7v33cb4BVvWdLIt477b9YFZO8NaVC4KPijQuXUDQpSvzOaryA== ARC-Authentication-Results: i=1; thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724542428; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references:dkim-signature; bh=unO/x9iA49MT6dTsa9kuPTwBviCMe7odiMKI7yTyolU=; b=fayUxJ/uwItDNvFkGuZIRyr0vURB+8FsnWEMUBnDxJY4W+jyrcznhWqR6YDu0jY1Nn64ro kpSjKDTf0STQ44kib5Ol6qZchBPdjNI10D07K8Gn4QxC0kEesqDX1PQflG8qEYaeUoROd5 jvBZ4nkcagsKNagm1QAF4FAdbzCVYmwDtu+il5O54yQ6Bb6FceYAZ3iP8Q/ee4Y9wINT+M YD7VmBb2j8FHjMlbhWgoa1HQUitRX1qnZtniTyfZJViXd9VifNubR2dWJB8XH4ZtSoRnDB ovRFxPlJLZQcvuKvip7TahavPmi7DYzxM5uhLgTZK25Vsp5i0ZtXeV7vln42pA== Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "*.lerctr.org", Issuer "R10" (verified OK)) (Authenticated sender: ler/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4WrtYS0yspz1FvF for ; Sat, 24 Aug 2024 23:33:48 +0000 (UTC) (envelope-from ler@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=ler2019; h=Content-Type:Message-ID:References:In-Reply-To:Subject:To:From: Date:MIME-Version:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description; bh=unO/x9iA49MT6dTsa9kuPTwBviCMe7odiMKI7yTyolU=; b=TSQwi VUX2ZdhL645H19+wZ5wu9LygeWOIVbZsbl2R2Zh6LxzRz7EWpJHbSL79jfYyK9ISBD2+gk+sSDkBw 0Qlc0X1lFNsQrvUPiB0K+M4QUP/QNbtxHKgDhXgps4XonJ4HJkLD/MJcmn1nw5U/0d8S9UiYLx2MP jq6yssrpBnj81aO0G6pZQ8pylwbw+SrFihuqx32loEs58RlkcqJLwH7RdybuIltu6BFa5VK0vtAzu lIh57V+FPeOlZ30NqgZfKRw5eMDfs4iR+xhPoiYPC8uu5WiGOsaTfBm9j7q3KVi0G6oGAln80rAlV NSBLal6jWqg7lObEMS9SkORbr2Miw==; Authentication-Results: thebighonker.lerctr.org; iprev=pass (thebighonker.lerctr.org) smtp.remote-ip=192.147.25.65; auth=pass (LOGIN) smtp.auth=ler@lerctr.org; spf=softfail smtp.mailfrom=FreeBSD.org; arc=none Received-SPF: softfail (thebighonker.lerctr.org: transitioning domain of FreeBSD.org does not designate 192.147.25.65 as permitted sender) client-ip=192.147.25.65; envelope-from=ler@FreeBSD.org; helo=webmail.lerctr.org; Received: from thebighonker.lerctr.org ([192.147.25.65]:52929 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.98 (FreeBSD)) (envelope-from ) id 1si0Ex-00000000PO9-2JAc for freebsd-current@freebsd.org; Sat, 24 Aug 2024 18:33:44 -0500 Received: from syn-070-123-041-087.res.spectrum.com ([70.123.41.87]) by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Sat, 24 Aug 2024 18:33:41 -0500 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Date: Sat, 24 Aug 2024 18:33:41 -0500 From: Larry Rosenman To: Freebsd current Subject: Re: Missing Drivers? In-Reply-To: References: Message-ID: X-Sender: ler@FreeBSD.org Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_a46f2fe423b48a9fe8a7e923906cf206"; micalg=pgp-sha256 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_a46f2fe423b48a9fe8a7e923906cf206 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed anyone? On 08/21/2024 9:40 am, Larry Rosenman wrote: > Any chance of getting Bluetooth working on this box and/or any other > missing pieces? > > dmesg.boot: https://www.lerctr.org/~ler/ryzen/dmesg.boot > pciconf -lv: https://www.lerctr.org/~ler/ryzen/pciconf.txt > > Thanks1 -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 --=_a46f2fe423b48a9fe8a7e923906cf206 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=488 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEHjgknedhWzvJgwVzaXyZsatIp30FAmbKbdcACgkQaXyZsatI p30kbggApROFKGjR+bEm8UyRiH9QG1o+7NIChmQNqHuy4qeyhrgfjWEFyq5HSbGr tvJDOYRDJPEMaPdpDlelUtMlRENgs+5tAa9tko6Qj4iMbkVgHfZTgHQZLpkm6WeB z4PU9G9GqO4tWCJq17zA2caFuWpZbx5h1x6MAc9lPEtLJSbwsXcqBMpry44yOvwo Y2+StJRqe1nop9foFamCSJp35iQErCSNF1IEnmmSWHrRYI9MAv81StSu2DYUzhRi J8rJ2OAg2vU9bqkDLXsCDusuQ5ojoVfiCcFRDIFWuBmZpzzjZ/eiY0MtV2QPUpU1 NQg2dQfP5N2T0c4MtWqTvdxCI2+x4A== =IzWd -----END PGP SIGNATURE----- --=_a46f2fe423b48a9fe8a7e923906cf206-- From nobody Sun Aug 25 05:13:13 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ws2594sbQz5VKHw for ; Sun, 25 Aug 2024 05:13:17 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ws2592kmKz4bpH for ; Sun, 25 Aug 2024 05:13:17 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; none Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 8E0D2892B6; Sun, 25 Aug 2024 05:13:14 +0000 (UTC) Received: (from phk@localhost) by critter.freebsd.dk (8.18.1/8.16.1/Submit) id 47P5DDZF029200; Sun, 25 Aug 2024 05:13:13 GMT (envelope-from phk) Message-Id: <202408250513.47P5DDZF029200@critter.freebsd.dk> To: Bob Bishop cc: "current@freebsd.org" Subject: Re: powerd forgets top CPU frequency ? In-reply-to: From: "Poul-Henning Kamp" References: <202408241706.47OH6LfG023651@critter.freebsd.dk> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29198.1724562793.1@critter.freebsd.dk> Date: Sun, 25 Aug 2024 05:13:13 +0000 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU] X-Rspamd-Queue-Id: 4Ws2592kmKz4bpH -------- Bob Bishop writes: > Possibly buggy ACPI on the Thinkpad not reporting any frequency higher > than it's actually running at? But that wouldn't explain why restarting powerd helps ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From nobody Sun Aug 25 07:59:02 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ws5mS53bjz5VXmq for ; Sun, 25 Aug 2024 07:59:04 +0000 (UTC) (envelope-from SRS0=cvou=PY=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ws5mS1NHzz4qy1; Sun, 25 Aug 2024 07:59:04 +0000 (UTC) (envelope-from SRS0=cvou=PY=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Sun, 25 Aug 2024 09:59:02 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1724572742; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=cwxbaIu+wY5k53Topdrp+JMM8NLtZ/wj9+pIJl7+gWA=; b=K8HY/Kq2clb0y0dk5rgeUYdPekPCLcGgxs2AJ2Mf8DqvvnrfI5Fymdj5+IzRgn3wjMkK58 ZSCALOD/08yC0wPAG34eSJ/7WaAeEH3iYvKFKJI1eGo+lafBfrNNwxZkukSe335MYXs64Q eu7fLkm6gjgTCRvrFWxD/SEr1GZBx/dgM9rlHYMnRhHP62HlLAK2dPNF7k8Y25p0/Y0HqF P88kSybyPi57K1+juUq3I3a4DTQT5DqI/rhGKHiai7j24sCH7n1m+NryR3AAu7x5UNRkCq mhpRCNykSN6+g48265tH7RLRUsGiG1EfSIK5I9FgcAPg2iGB8Yst/+Ungabemw== From: Ronald Klop To: Larry Rosenman Cc: Freebsd current Message-ID: <1369491189.10431.1724572742128@localhost> In-Reply-To: References: Subject: Re: Missing Drivers? List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10430_1350960236.1724572741951" X-Mailer: Realworks (717.35) Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Queue-Id: 4Ws5mS1NHzz4qy1 ------=_Part_10430_1350960236.1724572741951 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Larry Rosenman Datum: zondag, 25 augustus 2024 01:33 Aan: Freebsd current Onderwerp: Re: Missing Drivers? > > anyone? > > On 08/21/2024 9:40 am, Larry Rosenman wrote: > > Any chance of getting Bluetooth working on this box and/or any other > missing pieces? > > > > dmesg.boot: https://www.lerctr.org/~ler/ryzen/dmesg.boot > > pciconf -lv: https://www.lerctr.org/~ler/ryzen/pciconf.txt > > > > Thanks1 > > -- > Larry Rosenman http://people.freebsd.org/~ler > Phone: +1 214-642-9640 E-Mail: ler@FreeBSD.org > US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010 > > > > > ubt0 on uhub1 ubt0: on usbus1 ubt1 on uhub1 ubt1: on usbus1 ubt1: ubt_attach:674: could not get two interfaces device_attach: ubt1 attach returned 6 ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout Device ubt0 seems to attach properly (at least no errors). Can you disable ubt1 and just use ubt0? ------=_Part_10430_1350960236.1724572741951 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

Van: Larry Rosenman <ler@FreeBSD.org>
Datum: zondag, 25 augustus 2024 01:33
Aan: Freebsd current <freebsd-current@freebsd.org>
Onderwerp: Re: Missing Drivers?

anyone?

On 08/21/2024 9:40 am, Larry Rosenman wrote:
> Any chance of getting Bluetooth working on this box and/or any other > missing pieces?
>
> dmesg.boot: https://www.lerctr.org/~ler/ryzen/dmesg.boot
> pciconf -lv: https://www.lerctr.org/~ler/ryzen/pciconf.txt
>
> Thanks1

-- 
Larry Rosenman                     http://people.freebsd.org/~ler
Phone: +1 214-642-9640                 E-Mail: ler@FreeBSD.org
US Mail: 13425 Ranch Road 620 N, Apt 718, Austin, TX 78717-1010
 
 
  
ubt0 on uhub1
ubt0: <MediaTek Inc. WirelessDevice, class 239/2, rev 2.10/1.00, addr 2> on usbus1
ubt1 on uhub1
ubt1: <MediaTek Inc. WirelessDevice, class 239/2, rev 2.10/1.00, addr 2> on usbus1
ubt1: ubt_attach:674: could not get two interfaces
device_attach: ubt1 attach returned 6
ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout

Device ubt0 seems to attach properly (at least no errors). Can you disable ubt1 and just use ubt0?
------=_Part_10430_1350960236.1724572741951-- From nobody Sun Aug 25 08:09:29 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ws60X1wPHz5VYf8 for ; Sun, 25 Aug 2024 08:09:32 +0000 (UTC) (envelope-from SRS0=cvou=PY=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ws60W6SWDz4tZH for ; Sun, 25 Aug 2024 08:09:31 +0000 (UTC) (envelope-from SRS0=cvou=PY=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Sun, 25 Aug 2024 10:09:29 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1724573370; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=IvYsOwZddqt9/kBymYr46WbTh3NNNEi5hXZ6g1PcSmQ=; b=Nz9VwhSyB7CNhz9ZGqrZT74taxXBs5gkFVj6SFS7BdCzLp/5DY5sw2GNHq6sawJ1Pxl3SQ 2Xk3cLtSd0z/O7eHKLqbB2WhJeQTj0MIhrud+JAfTMGnMRczWAKgYCtvyRUA0lecMVSzbQ 852wBz8mYvJKdhD3uCiqngdDW3gT4PYqxWeTdWWtSAovyeNH5i2+DYF9C6vmyRAdcadvd0 ZlQudWo7ZJSfErZkZBQKJeOv3Z9ZpH6yeWrbGWgOMAQHKaR6FLesnP3F1zossu5HuthWFh jUsgxqIJCw3ESA16Uu5TmC/892UG7iIbeUGKnDVHeeoL+rUAOSBG+i/9Os3tIw== From: Ronald Klop To: Poul-Henning Kamp Cc: Bob Bishop , "current@freebsd.org" Message-ID: <1264471055.10452.1724573369940@localhost> In-Reply-To: <202408250513.47P5DDZF029200@critter.freebsd.dk> References: <202408241706.47OH6LfG023651@critter.freebsd.dk> <202408250513.47P5DDZF029200@critter.freebsd.dk> Subject: Re: powerd forgets top CPU frequency ? List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10451_1828013607.1724573369937" X-Mailer: Realworks (717.35) Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Queue-Id: 4Ws60W6SWDz4tZH ------=_Part_10451_1828013607.1724573369937 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Poul-Henning Kamp Datum: zondag, 25 augustus 2024 07:13 Aan: Bob Bishop CC: "current@freebsd.org" Onderwerp: Re: powerd forgets top CPU frequency ? > > -------- > Bob Bishop writes: > > > Possibly buggy ACPI on the Thinkpad not reporting any frequency higher > > than it's actually running at? > > But that wouldn't explain why restarting powerd helps ? > > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > > > Hi, A bit weird to try to give suggestions knowing how experienced you are in FreeBSD. But here we go, 1. What does the sysctl about cpu frequencies say. Does that value decrease too? On my machine it is this: # sysctl dev.cpu | grep freq dev.cpu.0.freq_levels: 1500/-1 600/-1 dev.cpu.0.freq: 1500 2. Does https://www.freshports.org/sysutils/powerdxx/ exhibit the same issue? To rule out if it is in the binary or in the kernel. 3. out-of-the-box: are your CPUs similar? So, do both have the same top frequency? 4. And powerd(8) mentions a -v option: "Verbose mode. Messages about power changes will be printed to stdout and powerd will operate in the foreground." Does that print anything useful? Regards, Ronald. ------=_Part_10451_1828013607.1724573369937 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

Van: Poul-Henning Kamp <phk@phk.freebsd.dk>
Datum: zondag, 25 augustus 2024 07:13
Aan: Bob Bishop <rb@gid.co.uk>
CC: "current@freebsd.org" <current@FreeBSD.org>
Onderwerp: Re: powerd forgets top CPU frequency ?

--------
Bob Bishop writes:

> Possibly buggy ACPI on the Thinkpad not reporting any frequency higher
> than it's actually running at?

But that wouldn't explain why restarting powerd helps ?


-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
 


Hi,

A bit weird to try to give suggestions knowing how experienced you are in FreeBSD. But here we go,

1. What does the sysctl about cpu frequencies say. Does that value decrease too?
On my machine it is this:
# sysctl dev.cpu  | grep freq
dev.cpu.0.freq_levels: 1500/-1 600/-1
dev.cpu.0.freq: 1500

2. Does https://www.freshports.org/sysutils/powerdxx/ exhibit the same issue? To rule out if it is in the binary or in the kernel.

3. out-of-the-box: are your CPUs similar? So, do both have the same top frequency?

4. And powerd(8) mentions a -v option: "Verbose mode.  Messages about power changes will be printed to stdout and powerd will operate in the foreground."
Does that print anything useful?

Regards,
Ronald.
  ------=_Part_10451_1828013607.1724573369937-- From nobody Sun Aug 25 08:29:36 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ws6Rn3jkCz5Vb7p for ; Sun, 25 Aug 2024 08:29:41 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ws6Rn1bSTz42Km for ; Sun, 25 Aug 2024 08:29:39 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; none Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id A6E8D892B6; Sun, 25 Aug 2024 08:29:37 +0000 (UTC) Received: (from phk@localhost) by critter.freebsd.dk (8.18.1/8.16.1/Submit) id 47P8TawP031885; Sun, 25 Aug 2024 08:29:36 GMT (envelope-from phk) Message-Id: <202408250829.47P8TawP031885@critter.freebsd.dk> To: Ronald Klop cc: Bob Bishop , "current@freebsd.org" Subject: Re: powerd forgets top CPU frequency ? In-reply-to: <1264471055.10452.1724573369940@localhost> From: "Poul-Henning Kamp" References: <202408241706.47OH6LfG023651@critter.freebsd.dk> <202408250513.47P5DDZF029200@critter.freebsd.dk> <1264471055.10452.1724573369940@localhost> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <31883.1724574576.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Sun, 25 Aug 2024 08:29:36 +0000 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU] X-Rspamd-Queue-Id: 4Ws6Rn1bSTz42Km -------- Ronald Klop writes: > A bit weird to try to give suggestions knowing how experienced you are i= n FreeBSD. But here we go, I'm not very experienced with how modern CPU's are modulated :-) > 1. What does the sysctl about cpu frequencies say. Does that value decre= ase too? > On my machine it is this: > # sysctl dev.cpu | grep freq > dev.cpu.0.freq_levels: 1500/-1 600/-1 > dev.cpu.0.freq: 1500 Right now: dev.cpu.7.freq_levels: 2803/-1 dev.cpu.7.freq: 3103 dev.cpu.5.freq_levels: 2803/-1 dev.cpu.5.freq: 3103 dev.cpu.3.freq_levels: 2803/-1 dev.cpu.3.freq: 3103 dev.cpu.1.freq_levels: 2803/-1 dev.cpu.1.freq: 3103 dev.cpu.6.freq_levels: 2803/-1 dev.cpu.6.freq: 3103 dev.cpu.4.freq_levels: 2803/-1 dev.cpu.4.freq: 3103 dev.cpu.2.freq_levels: 2803/-1 dev.cpu.2.freq: 3103 dev.cpu.0.freq_levels: 2803/-1 dev.cpu.0.freq: 3103 > 2. Does https://www.freshports.org/sysutils/powerdxx/ exhibit the same i= ssue? To rule out if it is in the binary or in the kernel. Will try. > 3. out-of-the-box: are your CPUs similar? So, do both have the same top = frequency? Yes, it's a: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz > 4. And powerd(8) mentions a -v option: "Verbose mode. Messages about po= wer changes will be printed to stdout and powerd will operate in the foreg= round." > Does that print anything useful? Yes, that's where I noticed the "gradually run slower and slower"... Initially I thought it was some kind of thermal throttling, but leaving th= e computer idle overnight did not lead to automatic recovery, whereas reboots and as = far as I can tell, restarting powerd does. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From nobody Sun Aug 25 08:38:14 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ws6dk059Yz5VbVH for ; Sun, 25 Aug 2024 08:38:18 +0000 (UTC) (envelope-from SRS0=cvou=PY=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ws6dh6dRYz441F for ; Sun, 25 Aug 2024 08:38:16 +0000 (UTC) (envelope-from SRS0=cvou=PY=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Sun, 25 Aug 2024 10:38:14 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1724575095; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ISC95xqvQAdvaoYbgC2TCUqim1cYX+TBKMuwYawbaPA=; b=IBUrhzg7qi/sowJw0iaDC8NnIsS7jPtOh1xS/E0peh05Cm0VhfH74GhWltSrO5frSGJLCe CPz0gk/hYxUuDw2fLeJ5m0EAszUo3rlf1s8J2n58GPK+mjnSiclD+JSkc1ZM/R2LfsIkpP G/iWTmimfYrjNrKuHcZlh0lKrkz0gwpuAIWcg41BEWxjTZUVNczYhvtmNef1WrrsY5pF48 jt41/u0/9Iis9sW2ISL8QDIQWIaOaxQDL8xZQQDXCAS2Mc2E21jt+L1T5v4wY9bL6zHYpB 2rMZ3bUN6taIU7xxcTAxrDdRT+y3ZreA4DCmtF+O8VSUQMc785FEvIKjIIDQGg== From: Ronald Klop To: Poul-Henning Kamp Cc: Bob Bishop , "current@freebsd.org" Message-ID: <1273956903.13647.1724575094919@localhost> In-Reply-To: <202408250829.47P8TawP031885@critter.freebsd.dk> References: <202408241706.47OH6LfG023651@critter.freebsd.dk> <202408250513.47P5DDZF029200@critter.freebsd.dk> <1264471055.10452.1724573369940@localhost> <202408250829.47P8TawP031885@critter.freebsd.dk> Subject: Re: powerd forgets top CPU frequency ? List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_13646_67042762.1724575094907" X-Mailer: Realworks (717.35) Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Queue-Id: 4Ws6dh6dRYz441F ------=_Part_13646_67042762.1724575094907 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Poul-Henning Kamp Datum: zondag, 25 augustus 2024 10:29 Aan: Ronald Klop CC: Bob Bishop , "current@freebsd.org" Onderwerp: Re: powerd forgets top CPU frequency ? > > -------- > Ronald Klop writes: > > > A bit weird to try to give suggestions knowing how experienced you are in FreeBSD. But here we go, > > I'm not very experienced with how modern CPU's are modulated :-) > > > 1. What does the sysctl about cpu frequencies say. Does that value decrease too? > > On my machine it is this: > > # sysctl dev.cpu | grep freq > > dev.cpu.0.freq_levels: 1500/-1 600/-1 > > dev.cpu.0.freq: 1500 > > Right now: > dev.cpu.7.freq_levels: 2803/-1 > dev.cpu.7.freq: 3103 > dev.cpu.5.freq_levels: 2803/-1 > dev.cpu.5.freq: 3103 > dev.cpu.3.freq_levels: 2803/-1 > dev.cpu.3.freq: 3103 > dev.cpu.1.freq_levels: 2803/-1 > dev.cpu.1.freq: 3103 > dev.cpu.6.freq_levels: 2803/-1 > dev.cpu.6.freq: 3103 > dev.cpu.4.freq_levels: 2803/-1 > dev.cpu.4.freq: 3103 > dev.cpu.2.freq_levels: 2803/-1 > dev.cpu.2.freq: 3103 > dev.cpu.0.freq_levels: 2803/-1 > dev.cpu.0.freq: 3103 > > > 2. Does https://www.freshports.org/sysutils/powerdxx/ exhibit the same issue? To rule out if it is in the binary or in the kernel. > > Will try. > > > 3. out-of-the-box: are your CPUs similar? So, do both have the same top frequency? > > Yes, it's a: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz > > > 4. And powerd(8) mentions a -v option: "Verbose mode. Messages about power changes will be printed to stdout and powerd will operate in the foreground." > > Does that print anything useful? > > Yes, that's where I noticed the "gradually run slower and slower"... > > Initially I thought it was some kind of thermal throttling, but leaving the computer > idle overnight did not lead to automatic recovery, whereas reboots and as far as I > can tell, restarting powerd does. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > > > dev.cpu.7.freq_levels: 2803/-1 dev.cpu.7.freq: 3103 This is interesting by itself. According to the sysctl the CPU only has 1 frequency to select, which is 2803, but it is running on 3103. Maybe there is some other mechanism which influences the CPU freq on your machine. I hope somebody else can shine some light on this. Doesn't the output (or source) of powerd give some insight on why it makes the decisions it makes? Regards, Ronald. ------=_Part_13646_67042762.1724575094907 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

Van: Poul-Henning Kamp <phk@phk.freebsd.dk>
Datum: zondag, 25 augustus 2024 10:29
Aan: Ronald Klop <ronald-lists@klop.ws>
CC: Bob Bishop <rb@gid.co.uk>, "current@freebsd.org" <current@FreeBSD.org>
Onderwerp: Re: powerd forgets top CPU frequency ?

--------
Ronald Klop writes:

> A bit weird to try to give suggestions knowing how experienced you are in FreeBSD. But here we go,

I'm not very experienced with how modern CPU's are modulated :-)

> 1. What does the sysctl about cpu frequencies say. Does that value decrease too?
> On my machine it is this:
> # sysctl dev.cpu  | grep freq
> dev.cpu.0.freq_levels: 1500/-1 600/-1
> dev.cpu.0.freq: 1500

Right now:
    dev.cpu.7.freq_levels: 2803/-1
    dev.cpu.7.freq: 3103
    dev.cpu.5.freq_levels: 2803/-1
    dev.cpu.5.freq: 3103
    dev.cpu.3.freq_levels: 2803/-1
    dev.cpu.3.freq: 3103
    dev.cpu.1.freq_levels: 2803/-1
    dev.cpu.1.freq: 3103
    dev.cpu.6.freq_levels: 2803/-1
    dev.cpu.6.freq: 3103
    dev.cpu.4.freq_levels: 2803/-1
    dev.cpu.4.freq: 3103
    dev.cpu.2.freq_levels: 2803/-1
    dev.cpu.2.freq: 3103
    dev.cpu.0.freq_levels: 2803/-1
    dev.cpu.0.freq: 3103

> 2. Does https://www.freshports.org/sysutils/powerdxx/ exhibit the same issue? To rule out if it is in the binary or in the kernel.

Will try.

> 3. out-of-the-box: are your CPUs similar? So, do both have the same top frequency?

Yes, it's a: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz

> 4. And powerd(8) mentions a -v option: "Verbose mode.  Messages about power changes will be printed to stdout and powerd will operate in the foreground."
> Does that print anything useful?

Yes, that's where I noticed the "gradually run slower and slower"...

Initially I thought it was some kind of thermal throttling, but leaving the computer
idle overnight did not lead to automatic recovery, whereas reboots and as far as I
can tell, restarting powerd does.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


    dev.cpu.7.freq_levels: 2803/-1
    dev.cpu.7.freq: 3103


This is interesting by itself. According to the sysctl the CPU only has 1 frequency to select, which is 2803, but it is running on 3103. Maybe there is some other mechanism which influences the CPU freq on your machine. I hope somebody else can shine some light on this.
Doesn't the output (or source) of powerd give some insight on why it makes the decisions it makes?

Regards,
Ronald.
  ------=_Part_13646_67042762.1724575094907-- From nobody Sun Aug 25 08:40:19 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ws6h550Mqz5VbbM for ; Sun, 25 Aug 2024 08:40:21 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ws6h545h1z44tt for ; Sun, 25 Aug 2024 08:40:21 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Authentication-Results: mx1.freebsd.org; none Received: from critter.freebsd.dk (unknown [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id DAC0B892B6; Sun, 25 Aug 2024 08:40:19 +0000 (UTC) Received: (from phk@localhost) by critter.freebsd.dk (8.18.1/8.16.1/Submit) id 47P8eJM8032225; Sun, 25 Aug 2024 08:40:19 GMT (envelope-from phk) Message-Id: <202408250840.47P8eJM8032225@critter.freebsd.dk> To: Ronald Klop cc: Bob Bishop , "current@freebsd.org" Subject: Re: powerd forgets top CPU frequency ? In-reply-to: <1273956903.13647.1724575094919@localhost> From: "Poul-Henning Kamp" References: <202408241706.47OH6LfG023651@critter.freebsd.dk> <202408250513.47P5DDZF029200@critter.freebsd.dk> <1264471055.10452.1724573369940@localhost> <202408250829.47P8TawP031885@critter.freebsd.dk> <1273956903.13647.1724575094919@localhost> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <32223.1724575219.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Sun, 25 Aug 2024 08:40:19 +0000 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:1835, ipnet:130.225.0.0/16, country:EU] X-Rspamd-Queue-Id: 4Ws6h545h1z44tt -------- Ronald Klop writes: > This is interesting by itself. According to the sysctl the CPU only has = 1 frequency to select, which is 2803, but it is running on 3103. Maybe the= re is some = Yes, I've always had a bit of trouble understanding how these things fit t= ogether... (Also not the best laptop I've had in a number of other ways) > other mechanism which influences the CPU freq on your machine. I hope so= mebody else can shine some light on this. > Doesn't the output (or source) of powerd give some insight on why it mak= es the decisions it makes? Only stuff like: load 144%, current freq 3692 MHz ( 0), wanted freq 5606 MHz load 127%, current freq 3692 MHz ( 0), wanted freq 5606 MHz load 120%, current freq 3692 MHz ( 0), wanted freq 5606 MHz load 136%, current freq 3692 MHz ( 0), wanted freq 5606 MHz load 132%, current freq 3692 MHz ( 0), wanted freq 5606 MHz But it is not entirely obvious to me that powerd actually does anything... -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From nobody Sun Aug 25 09:31:09 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ws7r63SZJz5VgTY for ; Sun, 25 Aug 2024 09:32:22 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ws7r60BwYz4F78 for ; Sun, 25 Aug 2024 09:32:21 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1724578334; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=v77AUAK8pk4AKwF5JutNYp3u/OqE/J5tJAGJXvnrmqA=; b=fJA1Dq6sq6OBfH/z0qBf32YLwZf42DN/u2wRBZSneRoAvBmwXp5sdN553QwjWRyQLnXdRH rsv44OjjoKY4j6+zalGPZcraKjlMxPBoUFhY8yubD2bjdYM/PxVLXcAf/1erX3BH9+JFHf eZZOrjwXD+/UixW1YjDysrIWZ2QJGd4= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id d813a2f8 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sun, 25 Aug 2024 09:32:14 +0000 (UTC) Date: Sun, 25 Aug 2024 11:31:09 +0200 From: Emmanuel Vadot To: "Poul-Henning Kamp" Cc: Ronald Klop , Bob Bishop , "current@freebsd.org" Subject: Re: powerd forgets top CPU frequency ? Message-Id: <20240825113109.a296da0265815333540c6552@bidouilliste.com> In-Reply-To: <202408250840.47P8eJM8032225@critter.freebsd.dk> References: <202408241706.47OH6LfG023651@critter.freebsd.dk> <202408250513.47P5DDZF029200@critter.freebsd.dk> <1264471055.10452.1724573369940@localhost> <202408250829.47P8TawP031885@critter.freebsd.dk> <1273956903.13647.1724575094919@localhost> <202408250840.47P8eJM8032225@critter.freebsd.dk> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd15.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] X-Rspamd-Queue-Id: 4Ws7r60BwYz4F78 On Sun, 25 Aug 2024 08:40:19 +0000 "Poul-Henning Kamp" wrote: > -------- > Ronald Klop writes: > > > This is interesting by itself. According to the sysctl the CPU only has 1 frequency to select, which is 2803, but it is running on 3103. Maybe there is some > > Yes, I've always had a bit of trouble understanding how these things fit together... > > (Also not the best laptop I've had in a number of other ways) You likely have hwpstate, so powerd will do nothing. Try changing dev.hwpstate_intel..epp value and see if you manage to do what you want, otherwise you will need to disable hwpstate (it's doable with some hints iirc) and use powerd. Cheers, > > other mechanism which influences the CPU freq on your machine. I hope somebody else can shine some light on this. > > Doesn't the output (or source) of powerd give some insight on why it makes the decisions it makes? > > Only stuff like: > > load 144%, current freq 3692 MHz ( 0), wanted freq 5606 MHz > load 127%, current freq 3692 MHz ( 0), wanted freq 5606 MHz > load 120%, current freq 3692 MHz ( 0), wanted freq 5606 MHz > load 136%, current freq 3692 MHz ( 0), wanted freq 5606 MHz > load 132%, current freq 3692 MHz ( 0), wanted freq 5606 MHz > > But it is not entirely obvious to me that powerd actually does anything... > > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > -- Emmanuel Vadot From nobody Sun Aug 25 10:23:05 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ws8yg5DlWz5VlBW for ; Sun, 25 Aug 2024 10:23:07 +0000 (UTC) (envelope-from gbe@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ws8yg4Fpgz4Ksn; Sun, 25 Aug 2024 10:23:07 +0000 (UTC) (envelope-from gbe@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724581387; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Cy3nsJtIRCCDMEpiTd9qpCdz+bc1h0qS8UKNysLAn20=; b=fszGmue3wT/4d0Tj+19+9r/PMKWkDQSFQUE+ZPesESPqVr0qNXSDNi8WKCaVYj6rin0uIa FcUfxPu5CYXAQ7FeYsr1ZVSAhMXU7kwGGwHBJ9hOhB+YNVnk8u4gNou0JMo/ZM3125GkoB h61gNQp/KR//0bK2noi+W0INowZT/4S6+aWUXIU3Mjje7UNaMa7dQMXpCUrkRKaXVAN3yC w9g1C87SYFgBdNEw18YkDNyk68RBVGMrnKA85Un9hWeCNrwLTdSsGHLepEWgj3d4S821sj B0mdUyY4dDWYQ58xDjO8Q6xNZKfStLOOKP4GGjVpNEp961SKaDVu2m9JlVHLQw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1724581387; a=rsa-sha256; cv=none; b=O9SxvVp5E9NpQf/OgYEgfDhRbNR8XT9KQ2kAY9Lzo8jZlTWzV/ARJYLh9MJlSRBeaEONB8 IyFURHg/8D6w4Z+qBPA0SGsfCRkjegeXvtNJtUEff8bmujYXyWSQ4QSuNk8k56ysWPw8Xc fIBjAFPf6BRT/MdNsiCLDg2eB1IQvzCuj6v0FpGmrKSw3+M2juKBvVEW7BA0a7oEcU6gAr E7Ed69Mulv2XkBAsNTLVk7NcIHu+JhJBrlbQrDISQ60C8Ftjvxq/wLE8kObHfgMzQ6OfW0 2AhpbRP907KNwf42k4PhqWrBH40fZ1dG/fyteI4JmakYIlYaT168+spvxXkbIQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1724581387; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Cy3nsJtIRCCDMEpiTd9qpCdz+bc1h0qS8UKNysLAn20=; b=ms420NyPKyfuxvkjVlcvVL2yBZ3XGORTJRbEm0tLePACLRYyC6thbiewBqg8qkhKzKdPqr iFcHA7qN+stFm5kiMp9RocYkilfdMYCzgORpDlcYPqhf93UaG0DnEbBeO2mBtj80aZHAm0 n+FRTPAEVHOj1pPlxVV+0qMbDg37sDCoYAcXF18O86rfiLOcCROPIRDrNLP14HuXPdFdpZ 18MEx7hlyGpy5ioyztztWLTBtUnVwNspHm5TjAaNgPCxDeNv7HS+Fq3AIdpWAvMGSU+5hg nRvtNNMSzhIj5dvJmJ9DDNWtGVuCrbU+HjMKqO5fG2vi02Ld/q7NFpNb8kXPNg== Received: from localhost (p4fd8be5f.dip0.t-ipconnect.de [79.216.190.95]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: gbe) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Ws8yg1ZPlzFmR; Sun, 25 Aug 2024 10:23:07 +0000 (UTC) (envelope-from gbe@FreeBSD.org) Date: Sun, 25 Aug 2024 12:23:05 +0200 From: Gordon Bergling To: Warner Losh Cc: Gordon Bergling , FreeBSD Current Subject: Re: buildworld error Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="cL5z32b7+L13hro7" Content-Disposition: inline In-Reply-To: X-Url: X-Operating-System: Darwin 23.6.0 arm64 X-Host-Uptime: 12:20 up 16 days, 13:14, 3 users, load averages: 3.05 2.51 2.15 --cL5z32b7+L13hro7 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Warner, On Sat, Aug 24, 2024 at 03:21:16PM -0600, Warner Losh wrote: > On Sat, Aug 24, 2024 at 1:39=E2=80=AFPM Gordon Bergling = wrote: > > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote: > > > On Sat, Aug 24, 2024, 1:14=E2=80=AFPM Gordon Bergling wrote: > > > > I got the following buildworld error a recent -CURRENT > > > > > > > > =3D=3D=3D> stand/i386/pxeldr (all) > > > > `kldstat.o' is up to date. > > > > -14152 bytes available > > > > > > > > The same happens on stable/14: > > > > > > > > =3D=3D=3D> stand/i386/pxeldr (all) > > > > -22344 bytes available > > > > =3D=3D=3D> share/misc (all) > > > > --- loader --- > > > > *** [loader] Error code 1 > > > > > > > > make[5]: stopped in /storage/freebsd/src/stable/14/stand/i386/pxeldr > > > > 1 error > > > > > > > > src.conf looks like the following: > > > > WITH_BEARSSL=3D1 > > > > WITH_RETPOLINE=3D1 > > > > WITHOUT_CLEAN=3D1 > > > > > > > > I remove the whole obj directories and tried several full builds, b= ut > > the > > > > error persists for a while. > > > > > > > > Has any one a clue how to solve this? > > > > > > Either disable pxe, raise the pxe limit (though it may not work), or > > select > > > the 4th loader for pxeboot. > > > > > > The loader is too big on BIOS to enable all the options. > > > > I looked at src.conf(5), but didn't found a switch to disable pxe. What= I > > am > > wondering about is that no one is facing the problem, since this it is a > > pretty clean build without and special modifications, despite the ones > > mention > > above in the src.conf. > > > > Did you have a hint on how to disable pxe? > > >=20 > I was sure that I'd documented everything, but it seems not: >=20 > WITHOUT_LOADER_PXEBOOT=3Dt > PXEBOOT_DEFAULT_INTERP=3D4th > PXEBOOTSIZE?=3D525000 >=20 > I'll look to make sure I don't have a commit stuck in a branch somewhere.= =2E.. with this values in the src.conf(5) the build finally finished. But I wonder why I am the only person, who hits that problem since it is a very plain -CURRENT build on a Hyper-V instance. Should these values be default values? --Gordon --cL5z32b7+L13hro7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEYbWI0KY5X7yH/Fy4OQX2V8rP09wFAmbLBggACgkQOQX2V8rP 09yUeQgA7kbGCZOPLFYTs3rDOcAXrGudN4LMSgd8CW16ws8xV88m/1VzxWCzVuPw 4J5MKUe6smplgph4JGjjM39tA7rs1SRAglWZsO9//5jQrPMj2mXNDwYUkZKUQNos 9aIhAkUNphgyhmQi3Qdceplfsq7ib/ycfGZAlWL5QHg9kbhtm1q07L01a1jz4T/e 1K8/vrhfeDVD+cGMoPtLogy8rxskdHjhVSnwgXg4iZZOyZNx+CPfZQVxzgnaaCyp toKoyWEN1QyQhGgtkKF0wxFrQ3hYm1CoHIjvsoW16G6bsjy4ZKJSZYyRXxkFwgGg 4CBtp7WiATmiilbTUCIY4E3sJE2N7Q== =BSNf -----END PGP SIGNATURE----- --cL5z32b7+L13hro7-- From nobody Sun Aug 25 10:35:41 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Ws9FW2Kvgz5Vlj3 for ; Sun, 25 Aug 2024 10:35:59 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from gid2.gid.co.uk (ns0.gid.co.uk [IPv6:2001:470:94de::240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gid2.gid.co.uk", Issuer "gid2.gid.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ws9FV5xBBz4MSh for ; Sun, 25 Aug 2024 10:35:58 +0000 (UTC) (envelope-from rb@gid.co.uk) Authentication-Results: mx1.freebsd.org; none Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by gid2.gid.co.uk (8.15.2/8.15.2) with ESMTP id 47PAZvnv075744; Sun, 25 Aug 2024 11:35:57 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from smtpclient.apple (moriarty.gid.co.uk [194.32.164.17]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id 47PAZpgF016261; Sun, 25 Aug 2024 11:35:51 +0100 (BST) (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=us-ascii List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\)) Subject: Re: powerd forgets top CPU frequency ? From: rb@gid.co.uk In-Reply-To: <202408250513.47P5DDZF029200@critter.freebsd.dk> Date: Sun, 25 Aug 2024 11:35:41 +0100 Cc: "current@freebsd.org" Content-Transfer-Encoding: 7bit Message-Id: References: <202408241706.47OH6LfG023651@critter.freebsd.dk> <202408250513.47P5DDZF029200@critter.freebsd.dk> To: Poul-Henning Kamp X-Mailer: Apple Mail (2.3774.600.62) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Queue-Id: 4Ws9FV5xBBz4MSh On 25 Aug 2024, at 06:13, Poul-Henning Kamp wrote: > > -------- > Bob Bishop writes: > >> Possibly buggy ACPI on the Thinkpad not reporting any frequency higher >> than it's actually running at? > > But that wouldn't explain why restarting powerd helps ? Maybe reattaching to cpufreq resets something? > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > -- Bob Bishop rb@gid.co.uk From nobody Sun Aug 25 17:01:46 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WsKpq0jTkz5T90L for ; Sun, 25 Aug 2024 17:01:55 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.infocus-llc.com (mail.infocus-llc.com [IPv6:2604:3a00:2:1::2:13]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WsKpp4c1zz4vcq for ; Sun, 25 Aug 2024 17:01:54 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Authentication-Results: mx1.freebsd.org; none Received: from draco.over-yonder.net (c-174-180-135-60.hsd1.ms.comcast.net [174.180.135.60]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.tarragon.infocus-llc.com (Postfix) with ESMTPSA id 4WsKpg0kWkzD3H; Sun, 25 Aug 2024 12:01:47 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 4WsKpf1fTCz11kB; Sun, 25 Aug 2024 12:01:46 -0500 (CDT) Date: Sun, 25 Aug 2024 12:01:46 -0500 From: "Matthew D. Fuller" To: Ronald Klop Cc: Poul-Henning Kamp , Bob Bishop , "current@freebsd.org" Subject: Re: powerd forgets top CPU frequency ? Message-ID: References: <202408241706.47OH6LfG023651@critter.freebsd.dk> <202408250513.47P5DDZF029200@critter.freebsd.dk> <1264471055.10452.1724573369940@localhost> <202408250829.47P8TawP031885@critter.freebsd.dk> <1273956903.13647.1724575094919@localhost> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1273956903.13647.1724575094919@localhost> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/2.2.13 (2024-03-09) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:33069, ipnet:2604:3a00::/32, country:US] X-Rspamd-Queue-Id: 4WsKpp4c1zz4vcq On Sun, Aug 25, 2024 at 10:38:14AM +0200 I heard the voice of Ronald Klop, and lo! it spake thus: > > This is interesting by itself. According to the sysctl the CPU only > has 1 frequency to select, which is 2803, but it is running on 3103. > Maybe there is some other mechanism which influences the CPU freq on > your machine. I hope somebody else can shine some light on this. This seems fairly common on more recent Intel stuff. On some systems (without powerd running, since it apparently doesn't do anything useful in such cases); dev.cpu.0.freq_levels: 3500/-1 dev.cpu.0.freq: 1801 dev.cpu.7.freq_levels: 3500/-1 dev.cpu.7.freq: 799 Xeon E3 v5 (Skylake) dev.cpu.0.freq_levels: 3500/-1 dev.cpu.0.freq: 900 dev.cpu.1.freq_levels: 3500/-1 dev.cpu.1.freq: 799 Xeon E-21xx (Coffee Lake) Seems to just all be done by the hardware. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From nobody Sun Aug 25 17:47:54 2024 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WsLrD2Qbjz5TDSX for ; Sun, 25 Aug 2024 17:48:12 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from gid2.gid.co.uk (ns0.gid.co.uk [IPv6:2001:470:94de::240]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gid2.gid.co.uk", Issuer "gid2.gid.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WsLrC6bwsz42H0 for ; Sun, 25 Aug 2024 17:48:11 +0000 (UTC) (envelope-from rb@gid.co.uk) Authentication-Results: mx1.freebsd.org; none Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by gid2.gid.co.uk (8.15.2/8.15.2) with ESMTP id 47PHmAU6076646; Sun, 25 Aug 2024 18:48:10 +0100 (BST) (envelope-from rb@gid.co.uk) Received: from smtpclient.apple (moriarty.gid.co.uk [194.32.164.17]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id 47PHm4x1043187; Sun, 25 Aug 2024 18:48:05 +0100 (BST) (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=utf-8 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\)) Subject: Re: powerd forgets top CPU frequency ? From: rb@gid.co.uk In-Reply-To: Date: Sun, 25 Aug 2024 18:47:54 +0100 Cc: Ronald Klop , Poul-Henning Kamp , "current@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <564EE1E4-D38D-4F20-B254-DDB4C7C56ED0@gid.co.uk> References: <202408241706.47OH6LfG023651@critter.freebsd.dk> <202408250513.47P5DDZF029200@critter.freebsd.dk> <1264471055.10452.1724573369940@localhost> <202408250829.47P8TawP031885@critter.freebsd.dk> <1273956903.13647.1724575094919@localhost> To: "Matthew D. Fuller" X-Mailer: Apple Mail (2.3774.600.62) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Queue-Id: 4WsLrC6bwsz42H0 Hi, > On 25 Aug 2024, at 18:01, Matthew D. Fuller = wrote: >=20 > On Sun, Aug 25, 2024 at 10:38:14AM +0200 I heard the voice of > Ronald Klop, and lo! it spake thus: >>=20 >> This is interesting by itself. According to the sysctl the CPU only >> has 1 frequency to select, which is 2803, but it is running on 3103. >> Maybe there is some other mechanism which influences the CPU freq on >> your machine. I hope somebody else can shine some light on this. >=20 > This seems fairly common on more recent Intel stuff. On some systems > (without powerd running, since it apparently doesn't do anything > useful in such cases); >=20 >=20 > dev.cpu.0.freq_levels: 3500/-1 > dev.cpu.0.freq: 1801 > dev.cpu.7.freq_levels: 3500/-1 > dev.cpu.7.freq: 799 >=20 > Xeon E3 v5 (Skylake) >=20 >=20 > dev.cpu.0.freq_levels: 3500/-1 > dev.cpu.0.freq: 900 > dev.cpu.1.freq_levels: 3500/-1 > dev.cpu.1.freq: 799 >=20 > Xeon E-21xx (Coffee Lake) Another data point: dev.cpu.0.freq_levels: 2401/100000 2400/100000 2300/93921 2200/88941 = 2100/84058 2000/79269 1900/74574 1800/69972 1700/64541 1600/60135 = 1500/55820 1400/51595 1300/47460 1200/43413 1100/38596 1000/34736 dev.cpu.0.freq: 2400 Xeon Silver 4210R (Cascade Lake) (2 packages) =E2=80=A6but this system is running 12.2R (and not powerd). Another = similar system, running powerd (but only 1 package) shows dev.cpu.0.freq = varying between 2400 and 1000 as expected. FWIW these are Intel boards. > Seems to just all be done by the hardware. >=20 >=20 > --=20 > Matthew Fuller (MF4839) | fullermd@over-yonder.net > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ > On the Internet, nobody can hear you scream. >=20 -- Bob Bishop rb@gid.co.uk From nobody Sun Aug 25 22:16:31 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WsSp40yWlz5TfPD for ; Sun, 25 Aug 2024 22:16:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WsSp36Fd5z4XR9 for ; Sun, 25 Aug 2024 22:16:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x52e.google.com with SMTP id 41be03b00d2f7-76cb5b6b3e4so2274786a12.1 for ; Sun, 25 Aug 2024 15:16:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1724624202; x=1725229002; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hwCqgq2a2XXpYTMj4uwBGJlgYkGXDhOxbO81LBzAczo=; b=mN2oYf+fgzyUX29EjbOtLiaUNi6vMBqBx5QmLOSnsVcf+fm+S/s88KwS6tM0C54pWU gjZyM1/rXkAzObzxQ3cpA0uChbg9jVyHmZRcXBe7IVwHoKvJzaxDnp46KIMZEGJs1zFF 7x29OvZkgUZ3RiOBGtQjjIunjMSE/RS/kuzwy91t1UjNdrW/eTGl+n9nKJXKzM2bDJh0 nVfImpHTtjWcpvKRtndLsJexe9AmjOyzKggPSWIgWGzaJXqrxgWo37wnJVXpe4Sa+Ndp KqjNdvohK+V+66oCFeMv0Cd3MfsVG8KzqhBBU2cIu5Wo1e0Gj81a2zKiV1UEKIRhsyj6 lOiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724624202; x=1725229002; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=hwCqgq2a2XXpYTMj4uwBGJlgYkGXDhOxbO81LBzAczo=; b=EKtu0FK1F71HjKgoEE73JIx7pw5Ly8I3If9HLPrIddLLw5NbCYm79W+50tVXuQRLsd pqVJq6EhbV3jSvGNtn6iJkI2Wan89PvqCx/i1Zp9erK7IdXS1GnMcLG8tPEXnoaeM5dL WdPZufdr0Cf0UAL1YIHXJnevuoHa87OcMRFNxCUEM873zgkriqB98EUpKr4pixhUWyul 9JNRGjaaIGIVfLPiFEduHp4lk1e4mAHxWWK/SnuxgabU6c/qgEJD880/a1aK+OclTFKS 0UfSoyiKnRANNzBOVQjZ0nocPjomuWGcK0dRzpL7EUul7vBpmEq9q67P/ykbUDXc3uLo eb8w== X-Gm-Message-State: AOJu0YxjhSu7NofSIbt4YocLHDn/2ZD/hiRhJ4hfmZdgJoTtno/Arm8p Gj1jtR/fDO+cCQApuKGGHHNSh6aJHJHn16MMs0jDpUeB9DhlPUvyO4/9SgQqauHx4sGlEobSDhR HGwYLDx3CovGRtrpkNemnWl1Lu1wfQdob+r8gCvAmRLap82bl X-Google-Smtp-Source: AGHT+IHGuOwFZXbB76gLvfLwM8jnC6KBWFEt7nkfYH5pLT6SfKDR5UW1KfDPp/CeeaWT2sZXqHEGlHlM6AkZ9ohopj8= X-Received: by 2002:a17:90b:2e83:b0:2d3:c05c:c51 with SMTP id 98e67ed59e1d1-2d64671d976mr7402646a91.0.1724624202172; Sun, 25 Aug 2024 15:16:42 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: In-Reply-To: From: Warner Losh Date: Sun, 25 Aug 2024 16:16:31 -0600 Message-ID: Subject: Re: buildworld error To: Gordon Bergling Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000f128410620895cae" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4WsSp36Fd5z4XR9 --000000000000f128410620895cae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Aug 25, 2024 at 4:23=E2=80=AFAM Gordon Bergling w= rote: > Hi Warner, > > On Sat, Aug 24, 2024 at 03:21:16PM -0600, Warner Losh wrote: > > On Sat, Aug 24, 2024 at 1:39=E2=80=AFPM Gordon Bergling wrote: > > > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote: > > > > On Sat, Aug 24, 2024, 1:14=E2=80=AFPM Gordon Bergling > wrote: > > > > > I got the following buildworld error a recent -CURRENT > > > > > > > > > > =3D=3D=3D> stand/i386/pxeldr (all) > > > > > `kldstat.o' is up to date. > > > > > -14152 bytes available > > > > > > > > > > The same happens on stable/14: > > > > > > > > > > =3D=3D=3D> stand/i386/pxeldr (all) > > > > > -22344 bytes available > > > > > =3D=3D=3D> share/misc (all) > > > > > --- loader --- > > > > > *** [loader] Error code 1 > > > > > > > > > > make[5]: stopped in > /storage/freebsd/src/stable/14/stand/i386/pxeldr > > > > > 1 error > > > > > > > > > > src.conf looks like the following: > > > > > WITH_BEARSSL=3D1 > > > > > WITH_RETPOLINE=3D1 > > > > > WITHOUT_CLEAN=3D1 > > > > > > > > > > I remove the whole obj directories and tried several full builds, > but > > > the > > > > > error persists for a while. > > > > > > > > > > Has any one a clue how to solve this? > > > > > > > > Either disable pxe, raise the pxe limit (though it may not work), o= r > > > select > > > > the 4th loader for pxeboot. > > > > > > > > The loader is too big on BIOS to enable all the options. > > > > > > I looked at src.conf(5), but didn't found a switch to disable pxe. > What I > > > am > > > wondering about is that no one is facing the problem, since this it i= s > a > > > pretty clean build without and special modifications, despite the one= s > > > mention > > > above in the src.conf. > > > > > > Did you have a hint on how to disable pxe? > > > > > > > I was sure that I'd documented everything, but it seems not: > > > > WITHOUT_LOADER_PXEBOOT=3Dt > > PXEBOOT_DEFAULT_INTERP=3D4th > > PXEBOOTSIZE?=3D525000 > > > > I'll look to make sure I don't have a commit stuck in a branch > somewhere.... > > with this values in the src.conf(5) the build finally finished. But I > wonder > why I am the only person, who hits that problem since it is a very plain > -CURRENT build on a Hyper-V instance. > > Should these values be default values? > You've enabled some big ticket items. It's not at all clear what the defaul= t should be when people grow the loader too big. These options exist because PXEBOOT larger than about 500k is know to be flakey, though there's no universally known good upper limit since it depends a lot on the BIOS, what it does, etc. So upping that limit is off the table (though one can if one tests it and finds that works). Some other people don't use PXE at all, so for them, disabling it makes the most sense. Still others can't up the PXE limit high enough, and for them, using the 4th loader is a good path forward. The other option is for someone to go through /boot/loader and shaving some additional space. I've found all the easy, low-hanging fruit, plus turning off all the esoteric filesystems got us down to almost fitting. Warner --000000000000f128410620895cae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Aug 25, 2024 at 4:23=E2=80=AF= AM Gordon Bergling <gbe@freebsd.org> wrote:
Hi= Warner,

On Sat, Aug 24, 2024 at 03:21:16PM -0600, Warner Losh wrote:
> On Sat, Aug 24, 2024 at 1:39=E2=80=AFPM Gordon Bergling <gbe@freebsd.org> wrote: > > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote:
> > > On Sat, Aug 24, 2024, 1:14=E2=80=AFPM Gordon Bergling <gbe@freebsd.org> = wrote:
> > > > I got the following buildworld error a recent -CURRENT<= br> > > > >
> > > > =3D=3D=3D> stand/i386/pxeldr (all)
> > > > `kldstat.o' is up to date.
> > > > -14152 bytes available
> > > >
> > > > The same happens on stable/14:
> > > >
> > > > =3D=3D=3D> stand/i386/pxeldr (all)
> > > > -22344 bytes available
> > > > =3D=3D=3D> share/misc (all)
> > > > --- loader ---
> > > > *** [loader] Error code 1
> > > >
> > > > make[5]: stopped in /storage/freebsd/src/stable/14/stan= d/i386/pxeldr
> > > > 1 error
> > > >
> > > > src.conf looks like the following:
> > > > WITH_BEARSSL=3D1
> > > > WITH_RETPOLINE=3D1
> > > > WITHOUT_CLEAN=3D1
> > > >
> > > > I remove the whole obj directories and tried several fu= ll builds, but
> > the
> > > > error persists for a while.
> > > >
> > > > Has any one a clue how to solve this?
> > >
> > > Either disable pxe, raise the pxe limit (though it may not w= ork), or
> > select
> > > the 4th loader for pxeboot.
> > >
> > > The loader is too big on BIOS to enable all the options.
> >
> > I looked at src.conf(5), but didn't found a switch to disable= pxe. What I
> > am
> > wondering about is that no one is facing the problem, since this = it is a
> > pretty clean build without and special modifications, despite the= ones
> > mention
> > above in the src.conf.
> >
> > Did you have a hint on how to disable pxe?
> >
>
> I was sure that I'd documented everything, but it seems not:
>
> WITHOUT_LOADER_PXEBOOT=3Dt
> PXEBOOT_DEFAULT_INTERP=3D4th
> PXEBOOTSIZE?=3D525000
>
> I'll look to make sure I don't have a commit stuck in a branch= somewhere....

with this values in the src.conf(5) the build finally finished. But I wonde= r
why I am the only person, who hits that problem since it is a very plain -CURRENT build on a Hyper-V instance.

Should these values be default values?

= You've enabled some big ticket items. It's not at all clear what th= e default
should be when people grow the loader too big. These op= tions exist because
PXEBOOT=C2=A0larger than about 500k is know t= o be flakey, though there's no
universally known good upper l= imit since it depends a lot on the BIOS, what
it does, etc. So up= ping that limit is off the table (though one can if one tests
it = and finds that works). Some other people don't use PXE at all, so for
them, disabling it makes the most sense. Still others can't up= the PXE
limit high enough, and for them, using the 4th loader is= a good path
forward.

The other option i= s for someone to go through /boot/loader and shaving
some additio= nal space. I've found all the easy, low-hanging fruit, plus
t= urning off all the esoteric filesystems got us down to almost fitting.

Warner
--000000000000f128410620895cae--