Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Jul 2024 22:34:13 -0400
From:      "Drew Gallatin" <gallatin@freebsd.org>
To:        "Konstantin Belousov" <kostikbel@gmail.com>
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:  <ea778ca5-6567-4fed-b894-9ed27bbb2f71@app.fastmail.com>
In-Reply-To: <ZqQAudgNRShMg94D@kib.kiev.ua>
References:  <202405060315.4463FxP6098471@gitrepo.freebsd.org> <52e1bb60-32f3-49de-9714-78762edbfd4c@app.fastmail.com> <ZqQAudgNRShMg94D@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
--d78273312bf64c0f8daf716107e09c82
Content-Type: text/plain


Thank you!
On Fri, Jul 26, 2024, at 4:02 PM, Konstantin Belousov wrote:
> 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.
> 

--d78273312bf64c0f8daf716107e09c82
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div><br></div><div>=
Thank you!<br></div><div>On Fri, Jul 26, 2024, at 4:02 PM, Konstantin Be=
lousov wrote:<br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><d=
iv>On Fri, Jul 26, 2024 at 01:14:23PM -0400, Drew Gallatin wrote:<br></d=
iv><div>&gt; Hi,<br></div><div>&gt;&nbsp;<br></div><div>&gt; This recent=
ly hit our tree and was deployed, and our operations team is quite upset=
 because this results in a massive (orders of magnitude)&nbsp; increase =
in our kernel log messages due to our monitoring scripts probing each po=
rt.<br></div><div>&gt;&nbsp;<br></div><div>&gt; Can we please move this =
under bootverbose, or have some other way to suppress these prints?&nbsp=
; I can back this out in our tree, but I don't want to create yet anothe=
r local patch.<br></div><div>&gt;&nbsp;<br></div><div>I will put it unde=
r bootverbose.<br></div><div><br></div></blockquote><div><br></div></bod=
y></html>
--d78273312bf64c0f8daf716107e09c82--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ea778ca5-6567-4fed-b894-9ed27bbb2f71>