Re: Long time outdated jemalloc
On Sunday, July 21st, 2024 at 6:54 AM, Warner Losh wrote: > On Sat, Jul 20, 2024 at 1:59 AM cglogic wrote: > >> Hello FreeBSD community, >> >> After Jason Evans stepped aside from maintaining jemalloc in FreeBSD, it's >> not updating in time anymore. >> Version 5.3.0 was released May 6, 2022 and FreeBSD still not imported it >> into the tree. >> >> There is a pending review https://reviews.freebsd.org/D41421 from Aug 11, >> 2023. >> I'm successfully running FreeBSD/amd64 system with D41421 applied for 8 >> months, as well as many other people. >> >> Can it be reviewed and committed to CURRENT? >> Or, if there is no committers willing to do it, can commit bit be given to >> submitter or another person willing to do this? >> >> It's very disappointing when users spend their time to fill such gaps and >> their efforts just ignored by the developers. >> >> Every year FreeBSD Community Survey asking about user experience in >> contributing to FreeBSD. >> >> Here you can see an example of such contributing. > > First, thank you for being persistent and continuing to bring it up. It's > important to do that to make sure this (and your many other) contribution > doesn't fall on the floor. > > And to be fair, we're only 3 months since the last update. Still, quite a bit > longer than you should have to wait, but not nearly the year the original > date suggests. > > And this is a perfect storm of "how the project is bad at accepting > contributions": > (1) The original submission was close to the 14 branch creation time. This > meant that we weren't well prepared to look at it since it is such an > invasive change (at least on its surface). It also slowed the initial > response... > (2) There was a number of back and forth requests for changes, which took > time to sort out... > (3) The size of this is huge, well beyond the capacity of Phabricator to > review accurately... > (4) It's a vendor import. That means we can't just drop the Phabricator > review into the tree... > (5) It's phabricator: this is a great tool for developers, but we have a > terrible track record of using it for intake from new contributors. We don't > have any oversight at all over this tool, at there's at best tepid and luke > warm attempts to look for drop balls. > > All of these things are a terrible experience. I can only apologize. These > days, we might steer this towards github, but the 'vendor import' means you > really need someone on the inside, or you need to be on the inside to make > that work. > > So, how to move forward? Well, I'd like to propose the following: > (1) submit all the other Phabricator reviews you have open (they are mostly > good, or close to good) to github. Github is being actively managed and will > make it faster to get things it. It's a much better tool for new contributors > (and even frequent contributors of smallish things). > (2) I should do an vendor import of 5.3.0 from github, and do the merge to a > branch and push that to github. You can then layer on your changes and those > can be reviewed more closely as a pull request against the branch I push. I > suspect that most of the issues are sorted out already > (3) I'll land it via that route... > > And, if the sum of the other pull requests and this are good (and I suspect > they will be), then we can talk about commit bits and such. > > It's experiences like this which is why I'm trying to stand up github pull > requests as a reliable way to get things and and the best place to send > people... > > Thanks again for persisting, and also for expressing this criticism that we > (hopefully) can use to make it better. > > Warner Hello. I'm not the author of D41421. Just applied the patch to test it 8 months ago. And recently discovered that it's still not committed. I can't copy your message to Phabricator because don't have an account. Please, if you have time, help the author in D41421. Thank you.
Long time outdated jemalloc
Hello FreeBSD community, After Jason Evans stepped aside from maintaining jemalloc in FreeBSD, it's not updating in time anymore. Version 5.3.0 was released May 6, 2022 and FreeBSD still not imported it into the tree. There is a pending review https://reviews.freebsd.org/D41421 from Aug 11, 2023. I'm successfully running FreeBSD/amd64 system with D41421 applied for 8 months, as well as many other people. Can it be reviewed and committed to CURRENT? Or, if there is no committers willing to do it, can commit bit be given to submitter or another person willing to do this? It's very disappointing when users spend their time to fill such gaps and their efforts just ignored by the developers. Every year FreeBSD Community Survey asking about user experience in contributing to FreeBSD. Here you can see an example of such contributing. Thanks for your time.
14.1-PRERELEASE boot stuck on feeding entropy
Hello, After upgrading from February's 14-stable amd64 to 14.1-PRERELEASE amd64 one of my systems can't boot anymore. Bootloader was, of course, updated. It's freezes on "Feeding entropy ." message. The system installed on pretty old Supermicro server with dual Intel Xeon E5620 CPU, uses BIOS boot method and has root on ZFS. This CPU has no integrated random number generator, if I recall correctly. When I managed to boot this machine from recent 14.1-PRERELEASE installation media, mounted zroot to temporary dir, removed /boot/entropy file and rebooted it, the system booted. However next reboot it can't boot again, with the same "Feeding entropy ." last message. More modern hardware not affected by this issue. Thanks.
Re: 14-ALPHA2 panic on cold boot
Just tested 14.0-BETA5 and the issue is no longer present. My gratitude to Mark and all involved. --- Original Message --- On Monday, September 25th, 2023 at 12:12 PM, Mark Johnston wrote: > Yes. I've been traveling for the past couple of weeks and so haven't been > committing patches, but I'll be home tomorrow and plan to commit and merge > D41883. > > On Mon., Sep. 25, 2023, 06:59 cglogic, wrote: > >> Any chance that https://reviews.freebsd.org/D41883 will be merged into 14.0 >> before release? >> >> --- Original Message --- >> On Sunday, September 10th, 2023 at 5:14 PM, cglogic >> wrote: >> >>> For those who interested or affected by this issue. >>> >>> Looks like this regression was introduced by >>> https://reviews.freebsd.org/D34117 >>> Currently active PR is >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393 >>> It contains a patch proposed by one of users. >>> But the PR can't move forward without committers attention. >>> >>> --- Original Message --- >>> On Tuesday, August 29th, 2023 at 11:09 AM, cglogic >>> wrote: >>> >>>> Hello dear FreeBSD community, >>>> >>>> Recently I tried to boot from FreeBSD 14-ALPHA2 image and got panic on >>>> first boot after power on. >>>> My hardware is AMD Ryzen 9 5900X on ASUS ROG STRIX B550-E GAMING. >>>> It's related to audio chip ALC1220 initialization. >>>> >>>> If I remember correctly, when I tried FreeBSD 13-STABLE, around 2 years >>>> ago, no panic was observed. >>>> But at that time my GPU was unsupported by drm-kmod. So I installed Linux >>>> and used it for 2 years. >>>> On Linux, no such a panic observed. Now drm-kmod supports my GPU and I >>>> want move to FreeBSD. >>>> >>>> Also tried 13.2, got the same panic. >>>> Can't try earlier FreeBSD 13 releases, as they are not available for >>>> download anymore. >>>> >>>> I found two related bug reports: >>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264305 >>>> >>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393 >>>> >>>> My backtrace is the same as in reported issues. So I did not write it from >>>> a screen to a paper. >>>> >>>> As I understand, this bug affects all AMD Zen2, Zen3 and Zen4 computers >>>> and laptops. >>>> >>>> We are near FreeBSD 14.0 release now, maybe it will be possible to fix it >>>> before release. >>>> >>>> Thanks.
Re: 14-ALPHA2 panic on cold boot
Hi, All information already provided in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393 and https://reviews.freebsd.org/D41883 contains the fix. But it's not committed into CURRENT yet, so no reason to test 14.0 BETA3. The question is can the fix be committed and merged into 14.0 before release. Thanks. --- Original Message --- On Monday, September 25th, 2023 at 11:26 AM, Santiago Martinez wrote: > Hi there, > FreeBSD 14.0-beta3 is now avail, have you tried it? > Also can you provide the dump or logs from the crash/panic? > Best regards. > > Santi > > On 8/29/23 10:09, cglogic wrote: > >> Hello dear FreeBSD community, >> >> Recently I tried to boot from FreeBSD 14-ALPHA2 image and got panic on first >> boot after power on. >> My hardware is AMD Ryzen 9 5900X on ASUS ROG STRIX B550-E GAMING. >> It's related to audio chip ALC1220 initialization. >> >> If I remember correctly, when I tried FreeBSD 13-STABLE, around 2 years ago, >> no panic was observed. >> But at that time my GPU was unsupported by drm-kmod. So I installed Linux >> and used it for 2 years. >> On Linux, no such a panic observed. Now drm-kmod supports my GPU and I want >> move to FreeBSD. >> >> Also tried 13.2, got the same panic. >> Can't try earlier FreeBSD 13 releases, as they are not available for >> download anymore. >> >> I found two related bug reports: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264305 >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393 >> >> My backtrace is the same as in reported issues. So I did not write it from a >> screen to a paper. >> >> As I understand, this bug affects all AMD Zen2, Zen3 and Zen4 computers and >> laptops. >> We are near FreeBSD 14.0 release now, maybe it will be possible to fix it >> before release. >> >> Thanks.
Re: 14-ALPHA2 panic on cold boot
Any chance that https://reviews.freebsd.org/D41883 will be merged into 14.0 before release? --- Original Message --- On Sunday, September 10th, 2023 at 5:14 PM, cglogic wrote: > For those who interested or affected by this issue. > > Looks like this regression was introduced by > https://reviews.freebsd.org/D34117 > Currently active PR is > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393 > It contains a patch proposed by one of users. > But the PR can't move forward without committers attention. > > --- Original Message --- > On Tuesday, August 29th, 2023 at 11:09 AM, cglogic > wrote: > >> Hello dear FreeBSD community, >> >> Recently I tried to boot from FreeBSD 14-ALPHA2 image and got panic on first >> boot after power on. >> My hardware is AMD Ryzen 9 5900X on ASUS ROG STRIX B550-E GAMING. >> It's related to audio chip ALC1220 initialization. >> >> If I remember correctly, when I tried FreeBSD 13-STABLE, around 2 years ago, >> no panic was observed. >> But at that time my GPU was unsupported by drm-kmod. So I installed Linux >> and used it for 2 years. >> On Linux, no such a panic observed. Now drm-kmod supports my GPU and I want >> move to FreeBSD. >> >> Also tried 13.2, got the same panic. >> Can't try earlier FreeBSD 13 releases, as they are not available for >> download anymore. >> >> I found two related bug reports: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264305 >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393 >> >> My backtrace is the same as in reported issues. So I did not write it from a >> screen to a paper. >> >> As I understand, this bug affects all AMD Zen2, Zen3 and Zen4 computers and >> laptops. >> >> We are near FreeBSD 14.0 release now, maybe it will be possible to fix it >> before release. >> >> Thanks.
Re: 14-ALPHA2 panic on cold boot
For those who interested or affected by this issue. Looks like this regression was introduced by https://reviews.freebsd.org/D34117 Currently active PR is https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393 It contains a patch proposed by one of users. But the PR can't move forward without committers attention. --- Original Message --- On Tuesday, August 29th, 2023 at 11:09 AM, cglogic wrote: > Hello dear FreeBSD community, > > Recently I tried to boot from FreeBSD 14-ALPHA2 image and got panic on first > boot after power on. > My hardware is AMD Ryzen 9 5900X on ASUS ROG STRIX B550-E GAMING. > It's related to audio chip ALC1220 initialization. > > If I remember correctly, when I tried FreeBSD 13-STABLE, around 2 years ago, > no panic was observed. > But at that time my GPU was unsupported by drm-kmod. So I installed Linux and > used it for 2 years. > On Linux, no such a panic observed. Now drm-kmod supports my GPU and I want > move to FreeBSD. > > Also tried 13.2, got the same panic. > Can't try earlier FreeBSD 13 releases, as they are not available for download > anymore. > > I found two related bug reports: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264305 > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393 > > My backtrace is the same as in reported issues. So I did not write it from a > screen to a paper. > > As I understand, this bug affects all AMD Zen2, Zen3 and Zen4 computers and > laptops. > > We are near FreeBSD 14.0 release now, maybe it will be possible to fix it > before release. > > Thanks.
Fresh openssh before 13.0 release
Hi there, Any chance to see fresh openssh in upcoming 13.0 release? Thanks. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
pam_zfs_key
Hi there! Is pam_zfs_key available in 13-CURRENT? I want to setup automatically loading zfs encryption keys for home datasets. Thanks! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
