Date: Fri, 26 Jul 2024 23:02:01 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Drew Gallatin <gallatin@freebsd.org> Cc: src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org Subject: Re: git: c097967b9af9 - main - mlx5en: add diagnostic in one more case of failed eeprom read preparation Message-ID: <ZqQAudgNRShMg94D@kib.kiev.ua> In-Reply-To: <52e1bb60-32f3-49de-9714-78762edbfd4c@app.fastmail.com> References: <202405060315.4463FxP6098471@gitrepo.freebsd.org> <52e1bb60-32f3-49de-9714-78762edbfd4c@app.fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 26, 2024 at 01:14:23PM -0400, Drew Gallatin wrote: > Hi, > > This recently hit our tree and was deployed, and our operations team is quite upset because this results in a massive (orders of magnitude) increase in our kernel log messages due to our monitoring scripts probing each port. > > Can we please move this under bootverbose, or have some other way to suppress these prints? I can back this out in our tree, but I don't want to create yet another local patch. > I will put it under bootverbose.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZqQAudgNRShMg94D>