Re: Update to the Release Engineering Team Roster
On Fri, 17 Nov 2023 23:52:40 + Glen Barber wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > FreeBSD community, > > It is with a heavy heart that I have decided to resign my role as the > Release Engineering Team Lead. > > Colin Percival will take over this role, and I will act as his Deputy > Lead unless and until he finds a more suitable person to fill this > role. > > Regardless, I do not have any immediate plans to resign from the RE > Team as a whole, and though Colin has proved during the 13.2-RELEASE > cycle that he is fully capable of overtaking this role, I will remain > active on the team and will be available to him to provide any > guidance or insights as needed. > > I personally want to thank Colin for accepting this role change. I > have worked with Colin for several years directly, and indirectly, > much longer than I can remember. > > As I am sure many of you all are aware, Colin served the Project as > the Security Officer for several years, and authored important > utilities used by many within the community, such as portsnap and > freebsd-update. > > I have sent and received acknowledgement from the Core Team of this > decision to step aside, which was well received and no objection to me > selecting Colin to be my successor had been posed. > > Colin, thank you, again, for overtaking this role, and as we > discussed, I will be here to provide any needed guidance, insight, or > information as you need. As I had mentioned to you, I do not have > any immediate plans to leave the Team, nor do I have any question in > my mind that you are the obvious successor to this role. > > I am proud to be able to hand over the proverbial torch to you, and > look very much forward to your successes as the Release Engineering > Team Lead. > > It has been an absolute pleasure to be able to serve you all to the > best of my abilities over the past several years. > > With my very best regards to all involved in the Project, and nothing > but the best intentions of the Project in mind. > > Glen > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAmVX/MgACgkQAxRYpUeP > 4pPLVg/9HW6nhw6EXTGqkrdibCkThurdasCqftkLSGrsABDj1AsErHbBnbO3W04G > KSVZ6Jw28JQNGUsprJwcAsJre8PXgL2iKOkIZTL31CYSBvQbfGEzIWTC+18oTQ6Q > d1uxqGcqoMcpPfFxSry8wnfxO7hYGabv38lPy2KipskCqq/3zVqsdVb6UxGdo+5Q > 0sis6OVh8KhNdcgOu+RTZr194KJogsdqqGll4pOQNMv/Qpy5e9JOqHgVXueseUC8 > 6GDHa990VLF22+DLgq3qzVS0xGLIOM5MuC0EjWJEjaq5bANEzQX0SvMEKQEbGLrI > MjBXGoJGTreBMr0VbCewhuDIiYy7DU5dtohvXvCx+UoBryT9qU1RKmRyRxxp3hQ4 > dcZUyZ3RarwmZfJBTs7ib2s9LztUlpyIRAU7gJ2vRKcegVTH/Fe1FuRZHOFHZf46 > kzHeIygER3nitPtJj9ePQgq97F2WBjRDZ5MSzwNWsOMknsbUKekIB9xshbhxlUw8 > 5ZN61k3frKM/dOcnLulsNHFaMGJaodDsxMuTKhJCEHvHWLXOin66WrfuHKbeqzVf > LDgMCWiHcM0GwrtzXR/aITVZmwyg096gZw0NLXtlNadY+PyQrg8R83DmOKTk0fWo > MYaMnWBcZM78DviTaBPhcblMtB5/IqrbJzqnJqsnCBEW2Z29qgs= > =sYrP > -END PGP SIGNATURE- > Hi Glen I find myself at a time where I could possibly lend a hand, would someone like me be able to help with r...@freebsd.org? Teach and I can learn I guess ... I tend to excel but totally unsure if I can fit the bill! Regards Matti
Re: [HEADS-UP] Quick update to 14.0-RELEASE schedule
On Wed, 15 Nov 2023 04:52:31 + Glen Barber wrote: > > > Ok. I do not know what exactly is your point, but releases are > > > never official until there is a PGP-signed email sent. The email > > > is intended for the general public of consumers of official > > > releases, not "yeah, but"s. > > > > That does not say that the freebsd-update bits will not change *until* > the official release announcement has been sent. > > In my past 15 years involved in the Project, I think we have been very > clear on that. > > A RELEASE IS NOT FINAL UNTIL THE PGP-SIGNED ANNOUNCEMENT IS SENT. > > I mean, c'mon, dude. > > We really, seriously, for all intents and purposes, cannot be any more > clear than that. > > So, yes, *IF* an update necessitates a new freebsd-update build, what > you are running is *NOT* official. > > For at least 15 years, we have all said the same entire thing. Here I have been tracking 14.0 release candidates Reminds me of when slashdot would announce a new release days before it was actually released and then someone would remind them of that I am using an Australian mirror so will probably need to wait an extra day to be on the safe side :-)
Re: nvme INVALID_FIELD in dmesg.boot
On Wed, 25 May 2022 09:58:54 -0400 Alexander Motin wrote: > On 25.05.2022 08:25, Matteo Riondato wrote: > > My dmesg.boot contains the following entries containing > > "INVALID_FIELD" about nvme (I use nda(4) for my nvme disks, with > > hw.nvme.use_nvd=0 in loader.conf): > > > > trismegistus ~ % grep -e 'nvme[0-9]\?' /var/run/dmesg.boot > > nvme0: mem 0xb861-0xb8613fff irq 40 at device > > 0.0 numa-domain 0 on pci7 > > nvme1: mem 0xb851-0xb8513fff irq 47 at device > > 0.0 numa-domain 0 on pci8 > > nvme2: mem 0xc5e1-0xc5e13fff irq 48 at device > > 0.0 numa-domain 0 on pci10 > > nvme3: mem 0xc5d1-0xc5d13fff irq 55 at device > > 0.0 numa-domain 0 on pci11 > > nvme0: SET FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:000b > > cdw11:031f nvme0: INVALID_FIELD (00/02) sqid:0 cid:15 cdw0:0 > > nvme1: SET FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:000b > > cdw11:031f nvme1: INVALID_FIELD (00/02) sqid:0 cid:15 cdw0:0 > > nvme2: SET FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:000b > > cdw11:031f nvme2: INVALID_FIELD (00/02) sqid:0 cid:15 cdw0:0 > > nvme3: SET FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:000b > > cdw11:031f nvme3: INVALID_FIELD (00/02) sqid:0 cid:15 cdw0:0 > > nda0 at nvme0 bus 0 scbus16 target 0 lun 1 > > nda0: nvme version 1.2 x4 (max x4) lanes PCIe Gen3 (max Gen3) link > > nda1 at nvme1 bus 0 scbus17 target 0 lun 1 > > nda1: nvme version 1.2 x4 (max x4) lanes PCIe Gen3 (max Gen3) link > > nda2 at nvme2 bus 0 scbus18 target 0 lun 1 > > nda2: nvme version 1.2 x4 (max x4) lanes PCIe Gen3 (max Gen3) link > > nda3 at nvme3 bus 0 scbus19 target 0 lun 1 > > nda3: nvme version 1.2 x4 (max x4) lanes PCIe Gen3 (max Gen3) link > > > > The disks seem to work fine, from what I can tell. > > > > Are the "INVALID_FIELD" messages harmless, or can they be avoided > > with some tuning, or maybe with some patch? > > Those messages mean that driver tried to enable certain types of > asynchronous events, but probably the hardware does not support some > of those. If you wish to experiment we could try to mask some of the > bits in nvme_ctrlr_configure_aer() function to find out which one > exactly, but for discontinued drives 4-5 years old it might not have > too much sense. It should not be critical unless you either overheat > them, or somehow else they fail and wish to report it. > I am intrigued to how you guru's know this, is it because you know the code well enough?
Re: sound patch for pop & crackles
On Wed, 12 Nov 2003 13:36:31 -0500 Mathew Kanner <[EMAIL PROTECTED]> wrote: > Hello All, > Could people experiencing pops and crackles try the attached > patch and set hw.snd.fragps=128. This patch also fixes select on > vchans. > > more details in > > http://www.freebsd.org/cgi/query-pr.cgi?pr=59208 > > Thanks, > --Mat I applied the patch to /usr/src/sys/dev/sound/pcm/channel.c but am not sure how to set hw.snd.fragsps=128. In my confusion I put it in /boot/loader.conf and rebooted. However, sysctl hw.snd.fragsps gives me sysctl: unknown oid 'hw.snd.fragsps'. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: build problems
On Sun, 09 Nov 2003 00:36:57 -0500 Jason <[EMAIL PROTECTED]> wrote: > I have had problems finishing buildworld and the problem is the same > each time the build fails. It has failed 4 times at > file:///usr/src/gnu/usr.bin/cvs/doc/. I have cvsuped 3 times in 2 > days. I am running 5.1. Any info you might have would be helpful. > Thanks, > Jason Are you using -02 optimizations in /etc/make.conf ? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: snd_csa issues in -CURRENT
On Sat, 30 Aug 2003 18:45:49 +1000 matti k <[EMAIL PROTECTED]> wrote: > On Fri, 29 Aug 2003 12:36:56 +0200 > Eirik Oeverby <[EMAIL PROTECTED]> wrote: > > > I might also point out that there are two distinct kinds of > > distortion happening: The click/pop/crackle kind of distortion, > > and one where a sound buffer is repeated over and over 5-10 times > > - as if the hardware has some kind of hickup. > > > > Again - this *only* happens in -CURRENT, not in -STABLE or in any > > other OS (tested OS/2, BeOS, Linux, winXX). > > > > Anyone? :) > > > > /Eirik > > I get the same pops/crackling but using a SB Live! > I think it started happening when I switched from 4.x to 5.x > The strange thing is that sound works fine after a reboot but some > hours after that I get the noises. It only happens with music > (mp3,ogg). I tried a sound card with a CS4630 chip and still got the same thing. Strange that it takes a while for the noises to appear. Anyway, I was fiddling with settings using XMMS to play mp3's and found changing either "resolution" from 16bit to 8bit or changing "down sample" from 1:1(44khz) to 1:2(22khz) fixes the problem. These settings are located under audio i/o plugins -> input plugins -> mpeg layer 1/2/3 player -> configure -> decoder. Also after using these settings (1:2(22khz)) for half an hour and then changing them back to defaults ... sound was good. I should add that running gkrellm (/ports/sysutils/gkrellm) _and_ having the cpu monitor enabled makes the noises much worse. Again, on my system this only occurs after several hours and of course if I reboot all is well. If nothing else at least I've found a way to avoid rebooting, I guess. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: snd_csa issues in -CURRENT
On Fri, 29 Aug 2003 12:36:56 +0200 Eirik Oeverby <[EMAIL PROTECTED]> wrote: > I might also point out that there are two distinct kinds of distortion > happening: The click/pop/crackle kind of distortion, and one where a > sound buffer is repeated over and over 5-10 times - as if the hardware > has some kind of hickup. > > Again - this *only* happens in -CURRENT, not in -STABLE or in any > other OS (tested OS/2, BeOS, Linux, winXX). > > Anyone? :) > > /Eirik I get the same pops/crackling but using a SB Live! I think it started happening when I switched from 4.x to 5.x The strange thing is that sound works fine after a reboot but some hours after that I get the noises. It only happens with music (mp3,ogg). $ uname -a FreeBSD platypus.freebsd.home 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Aug 24 21:53:30 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PLATY4 i386 dmesg attached dmesg Description: Binary data ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
