From: Leon Romanovsky <leon@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
Rajat Khandelwal <rajat.khandelwal@linux.intel.com>,
linux-pci@vger.kernel.org, netdev@vger.kernel.org,
rajat.khandelwal@intel.com, jesse.brandeburg@intel.com,
linux-kernel@vger.kernel.org, edumazet@google.com,
intel-wired-lan@lists.osuosl.org, kuba@kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
anthony.l.nguyen@intel.com, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH] igc: Mask replay rollover/timeout errors in I225_LMVP
Date: Tue, 3 Jan 2023 14:00:04 +0200 [thread overview]
Message-ID: <Y7QYxAhcUa2JtjSy@unreal> (raw)
In-Reply-To: <20230103115402.GA848993@bhelgaas>
On Tue, Jan 03, 2023 at 05:54:02AM -0600, Bjorn Helgaas wrote:
> On Tue, Jan 03, 2023 at 11:54:24AM +0200, Leon Romanovsky wrote:
> > On Sun, Jan 01, 2023 at 11:34:21AM +0100, Paul Menzel wrote:
> > > Am 01.01.23 um 09:32 schrieb Leon Romanovsky:
> > > > On Thu, Dec 29, 2022 at 05:56:40PM +0530, Rajat Khandelwal wrote:
> > > > > The CPU logs get flooded with replay rollover/timeout AER errors in
> > > > > the system with i225_lmvp connected, usually inside thunderbolt devices.
> > > > >
> > > > > One of the prominent TBT4 docks we use is HP G4 Hook2, which incorporates
> > > > > an Intel Foxville chipset, which uses the igc driver.
> > > > > On connecting ethernet, CPU logs get inundated with these errors. The point
> > > > > is we shouldn't be spamming the logs with such correctible errors as it
> > > > > confuses other kernel developers less familiar with PCI errors, support
> > > > > staff, and users who happen to look at the logs.
>
> > > > > --- a/drivers/net/ethernet/intel/igc/igc_main.c
> > > > > +++ b/drivers/net/ethernet/intel/igc/igc_main.c
>
> > > > > +static void igc_mask_aer_replay_correctible(struct igc_adapter *adapter)
>
> > > > Shouldn't this igc_mask_aer_replay_correctible function be implemented
> > > > in drivers/pci/quirks.c and not in igc_probe()?
> > >
> > > Probably. Though I think, the PCI quirk file, is getting too big.
> >
> > As long as that file is right location, we should use it.
> > One can refactor quirk file later.
>
> If a quirk like this is only needed when the driver is loaded,
This is always the case with PCI devices managed through kernel, isn't it?
Users don't care/aware about "broken" devices unless they start to use them.
Thanks
next prev parent reply other threads:[~2023-01-03 12:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 12:26 [PATCH] igc: Mask replay rollover/timeout errors in I225_LMVP Rajat Khandelwal
2023-01-01 7:27 ` [Intel-wired-lan] " Neftin, Sasha
2023-01-01 8:32 ` Leon Romanovsky
2023-01-01 10:34 ` [Intel-wired-lan] " Paul Menzel
2023-01-03 9:54 ` Leon Romanovsky
2023-01-03 11:54 ` Bjorn Helgaas
2023-01-03 12:00 ` Leon Romanovsky [this message]
2023-01-03 14:21 ` Bjorn Helgaas
2023-01-03 17:16 ` Leon Romanovsky
2023-01-04 6:31 ` Leon Romanovsky
2023-01-01 10:32 ` Paul Menzel
2023-01-02 17:38 ` Khandelwal, Rajat
[not found] <CO1PR11MB483539867F2BABC92F586F8696F49@CO1PR11MB4835.namprd11.prod.outlook.com>
2023-01-03 19:13 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y7QYxAhcUa2JtjSy@unreal \
--to=leon@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=helgaas@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=rajat.khandelwal@intel.com \
--cc=rajat.khandelwal@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).