Re: May 2024 stabilization week
Am 2024-05-28 06:24, schrieb Gleb Smirnoff: On Mon, May 27, 2024 at 01:00:24AM -0700, Gleb Smirnoff wrote: T> This is an automated email to inform you that the May 2024 stabilization week T> started with FreeBSD/main at main-n270422-cca0ce62f367, which was tagged as T> main-stabweek-2024-May. Monday night status update: - Updated my personal desktop and home router, no issues noticed. - Testing at Netflix is delayed due to several issues: the test cluster busy with other stuff, some small difficulties with merging, etc. Usually we run the test Monday night to Tuesday, but this time we plan to do it Tuesday to Wednesday. Regressions I am aware of and tracking: - Linuxulator too strict on Netlink (PR 279012) Replying to this email thread with your success reports as well as reporting any regressions is very much appreciated. Thanks! Intel 32bit users users which use ZFS may want to have https://cgit.FreeBSD.org/src/commit/?id=4c053c17f2c8a715988f215d16284879857ca376 Apart from that much more stable on my 30-jails + poudriere host than the src as from the middle of the month. Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF signature.asc Description: OpenPGP digital signature
Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error
Hi Gerrit, Not sure if it will break your setup, but this already happened with 13.2 (I cant recall the exact release). Drivers used to be ok, before 13.X and then I started to see many errors. That's why I was suggesting to have a pkg with if_bnxt to get releases as required without needing a P1/2/++ release. is it possible for you to test on that machine and see what happens or its prod? Santi On 5/28/24 08:40, Gerrit Kühn wrote: Am Mon, 27 May 2024 15:05:31 -0600 schrieb Warner Losh: I'd like it there, but I think this will need to be a EN to get it into 14.1 given the late date of this commit Unless we slip 14.1 for other reasons... I have systems running 14.0 that use onboard bnxt chipsets, seen no issues so far. Does this mean I'll have to stick with 14.0 as 14.1 will probably break the interfaces? cu Gerrit
Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error
Am Tue, 28 May 2024 10:59:00 +0200 schrieb Santiago Martinez : > Not sure if it will break your setup, but this already happened with > 13.2 (I cant recall the exact release). I have two machines with onboard NICs (Supermicro H12SSL-CT mainboards) running just fine. One is 13.3, the other is 14.0. > Drivers used to be ok, before 13.X and then I started to see many errors. No errors at all on my side here. Do you have onboard NICs or PCIe cards? From the bugreport linked in earliers mails I can also see that the firmware I have here appears to be much older than what other people use. The latest I have is 214.0.286.18. > is it possible for you to test on that machine and see what happens or > its prod? Well, the 13.3 is production, the 14.0 is configured and loaded with data, should actually go into production this week (that's why I was asking... :-). However, I do have a third system of the same hardware that is unused right now. I could do tests there (given I find some time). cu Gerrit smime.p7s Description: S/MIME cryptographic signature
Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error
Hi! *"The latest I have is 214.0.286.18"* Indeed, the firmware on my box is older, I cannot upgrade it right now, but it is on my to-do list. I'm also trying to apply the patch recommended by @Warner. I will keep you posted. Santi On 5/28/24 11:19, Gerrit Kühn wrote: Am Tue, 28 May 2024 10:59:00 +0200 schrieb Santiago Martinez: Not sure if it will break your setup, but this already happened with 13.2 (I cant recall the exact release). I have two machines with onboard NICs (Supermicro H12SSL-CT mainboards) running just fine. One is 13.3, the other is 14.0. Drivers used to be ok, before 13.X and then I started to see many errors. No errors at all on my side here. Do you have onboard NICs or PCIe cards? From the bugreport linked in earliers mails I can also see that the firmware I have here appears to be much older than what other people use. The latest I have is 214.0.286.18. is it possible for you to test on that machine and see what happens or its prod? Well, the 13.3 is production, the 14.0 is configured and loaded with data, should actually go into production this week (that's why I was asking... :-). However, I do have a third system of the same hardware that is unused right now. I could do tests there (given I find some time). cu Gerrit
Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error
Am Tue, 28 May 2024 11:25:09 +0200 schrieb Santiago Martinez : > *"The latest I have is 214.0.286.18"* > Indeed, the firmware on my box is older, I cannot upgrade it right now, > but it is on my to-do list. Same here, I guess (pkgver). It says dev.bnxt.0.ver.fw_ver: 214.4.9.10/pkg 214.0.286.18 on both systems. Also, I don't think I can upgrade the firmware separately, it comes with the mainboard's bios (which is the latest available). cu Gerrit smime.p7s Description: S/MIME cryptographic signature
Re: May 2024 stabilization week
Hi Gleb, On Mon, May 27, 2024 at 09:24:14PM -0700, Gleb Smirnoff wrote: Replying to this email thread with your success reports as well as reporting any regressions is very much appreciated. Thanks! Works fine, no issues on arm64.aarch64 where it's running nginx, monit and a poudriere instance. --
